提交 0d6f3ebf 编写于 作者: M Masanari Iida 提交者: Jonathan Corbet

Doc: nfs: Fix typos in Documentation/filesystems/nfs

This patch fix spelling typos found in Documentation/filesystems/nfs
Signed-off-by: NMasanari Iida <standby24x7@gmail.com>
Signed-off-by: NJonathan Corbet <corbet@lwn.net>
上级 4db1fa66
...@@ -49,13 +49,13 @@ forget_locks: ...@@ -49,13 +49,13 @@ forget_locks:
forget_delegations: forget_delegations:
A delegation is used to assure the client that a file, or part of a file, A delegation is used to assure the client that a file, or part of a file,
has not changed since the delegation was awarded. Clearing this list will has not changed since the delegation was awarded. Clearing this list will
force the client to reaquire its delegation before accessing the file force the client to reacquire its delegation before accessing the file
again. again.
recall_delegations: recall_delegations:
Delegations can be recalled by the server when another client attempts to Delegations can be recalled by the server when another client attempts to
access a file. This test will notify the client that its delegation has access a file. This test will notify the client that its delegation has
been revoked, forcing the client to reaquire the delegation before using been revoked, forcing the client to reacquire the delegation before using
the file again. the file again.
......
...@@ -218,7 +218,7 @@ NFS/RDMA Setup ...@@ -218,7 +218,7 @@ NFS/RDMA Setup
/vol0 192.168.0.0/255.255.255.0(fsid=0,rw,async,insecure,no_root_squash) /vol0 192.168.0.0/255.255.255.0(fsid=0,rw,async,insecure,no_root_squash)
The IP address(es) is(are) the client's IPoIB address for an InfiniBand The IP address(es) is(are) the client's IPoIB address for an InfiniBand
HCA or the cleint's iWARP address(es) for an RNIC. HCA or the client's iWARP address(es) for an RNIC.
NOTE: The "insecure" option must be used because the NFS/RDMA client does NOTE: The "insecure" option must be used because the NFS/RDMA client does
not use a reserved port. not use a reserved port.
......
...@@ -166,7 +166,7 @@ ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>: ...@@ -166,7 +166,7 @@ ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>:
Value gets exported by /proc/net/pnp which is often linked Value gets exported by /proc/net/pnp which is often linked
on embedded systems by /etc/resolv.conf. on embedded systems by /etc/resolv.conf.
<dns1-ip> IP address of secound nameserver. <dns1-ip> IP address of second nameserver.
Same as above. Same as above.
......
...@@ -64,8 +64,8 @@ table which are called by the nfs-client pnfs-core to implement the ...@@ -64,8 +64,8 @@ table which are called by the nfs-client pnfs-core to implement the
different layout types. different layout types.
Files-layout-driver code is in: fs/nfs/filelayout/.. directory Files-layout-driver code is in: fs/nfs/filelayout/.. directory
Objects-layout-deriver code is in: fs/nfs/objlayout/.. directory Objects-layout-driver code is in: fs/nfs/objlayout/.. directory
Blocks-layout-deriver code is in: fs/nfs/blocklayout/.. directory Blocks-layout-driver code is in: fs/nfs/blocklayout/.. directory
Flexfiles-layout-driver code is in: fs/nfs/flexfilelayout/.. directory Flexfiles-layout-driver code is in: fs/nfs/flexfilelayout/.. directory
objects-layout setup objects-layout setup
...@@ -91,7 +91,7 @@ The API to the login script is as follows: ...@@ -91,7 +91,7 @@ The API to the login script is as follows:
Usage: $0 -u <URI> -o <OSDNAME> -s <SYSTEMID> Usage: $0 -u <URI> -o <OSDNAME> -s <SYSTEMID>
Options: Options:
-u target uri e.g. iscsi://<ip>:<port> -u target uri e.g. iscsi://<ip>:<port>
(allways exists) (always exists)
(More protocols can be defined in the future. (More protocols can be defined in the future.
The client does not interpret this string it is The client does not interpret this string it is
passed unchanged as received from the Server) passed unchanged as received from the Server)
......
...@@ -57,7 +57,7 @@ the Kerberos tickets, that needs to be sent through the GSS layer in ...@@ -57,7 +57,7 @@ the Kerberos tickets, that needs to be sent through the GSS layer in
order to perform context establishment. order to perform context establishment.
B) It does not properly handle creds where the user is member of more B) It does not properly handle creds where the user is member of more
than a few housand groups (the current hard limit in the kernel is 65K than a few thousand groups (the current hard limit in the kernel is 65K
groups) due to limitation on the size of the buffer that can be send groups) due to limitation on the size of the buffer that can be send
back to the kernel (4KiB). back to the kernel (4KiB).
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册