NFS cache permissions
Bruno Galindro da Costa
bruno.galindro at gmail.com
Thu Nov 12 16:16:31 UTC 2009
> I don't recall what the Linux mount command defaults the NFS version
> to - please retest after mounting the export under version 3 or
> version 4. You can do this by specifying vers=3 or nfsvers=3 (or 4) on
> the mount command.
I´ve tried these:
# mount -t nfs4 192.168.1.1:/mnt/vol0/email/ /email/
mount.nfs4: mounting 192.168.1.1:/mnt/vol0/email/ failed, reason given
by server:
No such file or directory
# mount -t nfs -o vers=4 192.168.1.1:/mnt/vol0/email/ /email/
mount.nfs: an incorrect mount option was specified
# mount -t nfs -o nfsvers=4 192.168.1.1:/mnt/vol0/email/ /email/
mount.nfs: an incorrect mount option was specified
I think my server doesn´t support nfsv4. Reading the /proc/mounts,
I´ve noticed that other mount points (mounted with shares of the same
server) use nfs version 3.
# cat /proc/mounts
<other mount point>
.
.
192.168.1.1:/mnt/vol0/share/ /share nfs
rw,relatime,vers=3,rsize=262144,wsize=262144,hard,nointr,proto=tcp,timeo=600,retrans=2,sec=sys,addr=192.168.1.1
0 0
These mount points are mounted with this following command. This means
that both client and server are negotiating (by default) a nfs version
3.
# mount -t nfs 192.168.1.1:/mnt/share /share
> The fact that you specifically request a read and write size of 8k
> (the default for v2) implies that you might have a requirement to only
> handle version 2... is this the case?
No no. I´ve added that options because it provides more performance
with nfs2 (I don´t remember where I´ve found this information). This
option can be removed without problems to my case.
More information about the ubuntu-users
mailing list