Skip to contentSkip to conversation

Error mounting FC8 NFS server with 2.6.31-rc3 NFSv4 client.

DISCUSSION Ben Greear 1 participant 2 messages Jul 20, 2009

Subsystems (2)
lore
Share & tools
lore

Ben Greear

author
#0 lore raw

I tried mounting an NFS server running FC8 (2.6.26.8-57.fc8 kernel) using a Fedora 11 system running an un-patched 2.6.31-rc3 64-bit kernel.

I am not sure at all that the FC8 system is set up to handle NFSv4 properly, but I was expecting some sort of useful error if that was the case.

Instead, I get this continually spewing to /var/log/messages:

Error: state manager failed on NFSv4 server 192.168.100.6 with error 2
Error: state manager failed on NFSv4 server 192.168.100.6 with error 2
Error: state manager failed on NFSv4 server 192.168.100.6 with error 2
Error: state manager failed on NFSv4 server 192.168.100.6 with error 2
...

On the file-server, I see this:

Jul 19 04:47:59 fs2 kernel: nfs4_cb: server 192.168.100.196 not responding, timed out
Jul 19 04:49:29 fs2 kernel: nfs4_cb: server 192.168.100.196 not responding, timed out
Jul 19 04:49:29 fs2 ntpd[2585]: kernel time sync status change 0001
Jul 19 04:50:59 fs2 kernel: nfs4_cb: server 192.168.100.196 not responding, timed out

I added some debug patches (on top of my other patches, including those to nfs) and got some debug info:

It seems that nfs4_init_clientid is returning -2, and establish_clid is returning -2. This causes reclaim lease logic to fail, and that causes state manager to print out the error repeatedly. -2 means ENOENT.

As far as I can tell, the mount never completes, staying in D state and filling up logs (I deleted a 16GB /var/log/messages file a few minutes ago!)

The mount command I'm trying is:
mount -t nfs4 192.168.100.6:/export/tmp /mnt/lf/nfs4-0

My kernel config is found here:
http://www.candelatech.com/oss/i7_config.txt

Thanks,
Ben

Signature · 2 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com
author
#1 lore raw
Quoted 2 lines · Ben Greear

I tried mounting an NFS server running FC8 (2.6.26.8-57.fc8 kernel) using a Fedora 11 system running an un-patched 2.6.31-rc3 64-bit kernel.

Ok, seems you have to have things mis-configured to reproduce this:

I had my /etc/exports looking like this on the file-server:

/export/tmp 192.168.100.0/24(rw)

When I changed it to be:
/export/tmp 192.168.100.0/24(rw,fsid=0)

And mounted 192.168.100.6:/ instead of 192.168.100.6:/export/tmp then it mounts properly and appears to work just fine.

If I leave file-server configured properly with fsid=0, but try to mount 192.168.100.6:/export/tmp then I get an error about no such file or directory, which also appears to be correct behaviour.

Thanks,
Ben

Signature · 2 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com