- 论坛徽章:
- 3
|
你没有看清楚吧 哥们
rhel5.4
Mount options for nfs
Instead of a textual option string, parsed by the kernel, the nfs file system expects a binary argument of type
struct nfs_mount_data. The program mount itself parses the following options of the form 'tag=value', and puts
them in the structure mentioned: rsize=n, wsize=n, timeo=n, retrans=n, acregmin=n, acregmax=n, acdirmin=n,
acdirmax=n, actimeo=n, retry=n, port=n, mountport=n, mounthost=name, mountprog=n, mountvers=n, nfsprog=n,
nfsvers=n, namlen=n. The option addr=n is accepted but ignored. Also the following Boolean options, possibly
preceded by no are recognized: bg, fg, soft, hard, intr, posix, cto, ac, tcp, udp, lock. For details, see
nfs(5).
Especially useful options include
rsize=32768,wsize=32768
This causes the NFS client to try to negotiate a buffer size up to the size specified. A large buffer
size does improve performance, but both the server and client have to support it. In the case where one
of these does not support the size specified, the size negotiated will be the largest that both support.
intr This will allow NFS operations (on hard mounts) to be interrupted while waiting for a response from the
server.
nolock Do not use locking. Do not start lockd. |
|
免费注册
发表于 2010-09-08 09:55
