r7257 - NFS version\transport protocol not supported?

[survive]

Hi guys,

I'm still trying to verify, but I think there might be a problem with NFS in the latest nightly builds.

Here's what I know: I've been sharing storage via NFS to my ESXi server since I started running 8.0. Today I noticed that the share was disconnected in vcenter so I removed it via the client from Config -> Storage and tried to add it back uning "Add Storage...". That didn't work, I tried a couple more times and then I started looking through the ESXi logs. The only clue I found are 3 lines from /var/log/messages on ESXi (attached - ESXi_NFS_error.txt) telling me that "The NFS server does not support MOUNT version 3 over TCP".

Later I was on the IRC channel and saw a couple of users who were also trying to get an NFS share mounted (one to Ubuntu, the other to Windows 7). I asked if there was anything interesting in their logs and the Ubuntu user replied that ""mount.nfs: requested NFS version or transport protocol is not supported" was showing up in their logs. They were both running the latest (Saturday, 8-20-11 r7257) nightly build as well.

While I was talking to them I came across this post in the forums:

​http://forums.freenas.org/showthread.php?1784-NFS-logs

Basically a user who was working in Beta 4 had updated to r7248 and now NFS wasn't working for them.

So I figured it was time to open a ticket.

I honestly can't say when the NFS share to my ESXi box stopped working, but it must have been in the last week...I think I started running nightly builds at r7122...I hate to think it would have taken me over a week to notice the datastore was disconnected.

-Will

[survive]

NFS errors from ESXi host when mounting share.

[delphij]

Fixed in r7262.

[neubert]

I am currently testing r7263 and my linux client cannot mount my nfs shares either. Same for r7260. Beta-4 works. Sample verbose output from the linux client:

vserver1:~ # mount -vv -t nfs fs:/mnt/volume1/Users /data/Users
mount.nfs: timeout set for Mon Aug 22 20:56:25 2011
mount.nfs: trying text-based options 'vers=4,addr=192.168.31.12,clientaddr=192.168.31.2'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.31.12'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.31.12 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: prog 100003, trying vers=2, prot=6
mount.nfs: trying 192.168.31.12 prog 100003 vers 2 prot TCP port 2049
mount.nfs: prog 100005, trying vers=1, prot=17
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100005, trying vers=1, prot=6
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: prog 100003, trying vers=2, prot=6
mount.nfs: trying 192.168.31.12 prog 100003 vers 2 prot TCP port 2049
mount.nfs: prog 100005, trying vers=2, prot=17
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100005, trying vers=2, prot=6
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: requested NFS version or transport protocol is not supported

Kind regards,
Boris

[delphij]

Replying to neubert:

I am currently testing r7263 and my linux client cannot mount my nfs shares either. Same for r7260. Beta-4 works. Sample verbose output from the linux client:

This should have been fixed in r7266. Note you need either a full nightly build or change /conf/base/etc/rc.d plus /etc/rc.d if patching a live system.

Please let us know if there is still problem.

[neubert]

Hi,

today I installed r7296 and I can mount all FreeNAS nfs exports on my linux client.

Problem solved.

Thank you,

Boris

[delphij]

Replying to neubert:

Hi,

today I installed r7296 and I can mount all FreeNAS nfs exports on my linux client.

Problem solved.

Good to know, thanks!

[johny]

I am having the same exact issues with FreeNAS-8.0.1-RC1 (released 2011-08-31). Did this bug make it's way back into the current RC1?

[gcooper]

The code hasn't been changed in 2 weeks. Can you please open another ticket and attach your logs to that, referencing this bug?