I'm seeing the same behavior reported in #524760: i need to explicitly add nfsvers=2 to my mount options from a sid client running nfs-common 1:1.1.6-1 to a server running lenny's nfs-user-server 2.2beta47-25.
otherwise, the mount fails with this message (and with return code 32:
0 clam:/etc# mount /home/music
mount.nfs: mount to NFS server 'tunes:/srv/music/music' failed: RPC
Error: Success
32 clam:/etc#
I ran "rpcdebug -m nfs -s mount" to get more verbose information in the
dmesg.
Without nfsver=2 (or with nfsver=3 explicitly), dmesg shows this:
[ 5433.113573] NFS: nfs mount opts='addr=192.168.13.79'
[ 5433.113636] NFS: parsing nfs mount option 'addr=192.168.13.79'
[ 5433.113676] NFS: parsing IPv4 address 192.168.13.79
[ 5433.113705] NFS: MNTPATH: '/srv/music/music'
[ 5433.113723] NFS: sending MNT request for tunes:/srv/music/music
[ 5433.120476] NFS: failed to create RPC client, status=-93
[ 5433.120497] NFS: unable to mount server tunes, error -93
With nfsver=2, dmesg shows this:
[ 6430.525965] NFS: nfs mount opts='nfsvers=2,addr=192.168.13.79'
[ 6430.526030] NFS: parsing nfs mount option 'nfsvers=2'
[ 6430.526069] NFS: parsing nfs mount option 'addr=192.168.13.79'
[ 6430.526100] NFS: parsing IPv4 address 192.168.13.79
[ 6430.526126] NFS: MNTPATH: '/srv/music/music'
[ 6430.526145] NFS: sending MNT request for tunes:/srv/music/music
[ 6430.529771] NFS: MNT request succeeded
My current functional line in /etc/fstab on the client is:
tunes:/srv/music/music /home/music nfs
defaults,ro,nosuid,nodev,noexec,nfsvers=2 0 0
could this be an interaction with nfs-user-server? I can gather more
data if it would help.
--dkg
signature.asc
Description: OpenPGP digital signature
