[Solved] Suddently unable to mount nfs shares

[mark9117]

So, it's after 4:00 am and I'm totally stumped on this one.

For some reason, I am unable to mount nfs shares from one of my boxes on another. The nfs file host machine is 4.4.114-desktop-1.mga5, magia 5 and the client machine is also 4.4.114-desktop-1.mga5 mageia 5.

The server is installed from unfs3-0.9.22-7.mga5.x86_64.

As of last update and reboot of the client machine, I'm getting this error when I try to mount shares that used to work just fine:

Code: Select all

mount.nfs: requested NFS version or transport protocol is not supported

I'm not having any luck with Google on this.

Here is an example from the client's fstab:

Code: Select all

shuttle:/share/Music /mnt/shuttle/server/Music nfs rsize=8192,nosuid,wsize=8192,soft 0 0

I've tried mounting the shares manually, but that makes no difference. I'm not sure what to change.

The exports on the server look like this:

Code: Select all

# cat exports
# generated by drakhosts.pl
/share *(root_squash,anonuid=10001,anongid=10001,async,secure,no_subtree_check,rw)
/super *(root_squash,anonuid=10001,anongid=10001,async,secure,no_subtree_check,rw)
/home/madams *(no_all_squash,async,secure,no_subtree_check,rw)
/home/FTP-shared *(no_root_squash,no_all_squash,async,secure,no_subtree_check,rw)
/var/www/html *(root_squash,anonuid=10001,anongid=10001,async,secure,no_subtree_check,rw)
/share/Recipes *(root_squash,anonuid=10001,anongid=10001,async,secure,no_subtree_check,rw)
/share/Music *(root_squash,anonuid=10001,anongid=10001,async,secure,no_subtree_check,rw)


Showmounts:

Code: Select all

# showmount -e shuttle
Export list for shuttle:
/share/Music *
/share/Recipes *
/var/www/html *
/home/FTP-shared *
/home/madams *
/super *
/share *

The updates shouldn't have killed my nfs mounts that I can tell. Here is what the client got:

Code: Select all

rootcerts-java-20180411.00-1.mga5.noarch      Wed 25 Jul 2018 10:49:13 PM MDT
rootcerts-20180411.00-1.mga5.noarch           Wed 25 Jul 2018 10:49:13 PM MDT
nss-3.28.6-1.4.mga5.x86_64                    Wed 25 Jul 2018 10:49:12 PM MDT
lib64nss3-3.28.6-1.4.mga5.x86_64              Wed 25 Jul 2018 10:49:12 PM MDT
lib64nspr4-4.19-1.mga5.x86_64                 Wed 25 Jul 2018 10:49:11 PM MDT

The server got these:

Code: Select all

rootcerts-java-20180411.00-1.mga5.noarch      Wed 25 Jul 2018 10:48:44 PM MDT
rootcerts-20180411.00-1.mga5.noarch           Wed 25 Jul 2018 10:48:44 PM MDT
lib64gvc6-2.38.0-10.1.mga5.x86_64             Sun 22 Jul 2018 11:25:02 AM MDT
lib64gcrypt11-1.5.4-5.5.mga5.x86_64           Sun 22 Jul 2018 11:25:02 AM MDT
lib64pathplan4-2.38.0-10.1.mga5.x86_64        Sun 22 Jul 2018 11:25:01 AM MDT
lib64cgraph6-2.38.0-10.1.mga5.x86_64          Sun 22 Jul 2018 11:25:01 AM MDT
lib64cdt5-2.38.0-10.1.mga5.x86_64             Sun 22 Jul 2018 11:25:01 AM MDT


Quick edit: a verbose attempt to mount shows this:

Code: Select all

# mount -v -t nfs shuttle:/share/Music /mnt/shuttle/server/Music
mount.nfs: timeout set for Thu Jul 26 04:36:56 2018
mount.nfs: trying text-based options 'vers=4,addr=192.168.1.105,clientaddr=192.168.1.100'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.1.105'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: portmap query retrying: RPC: Program not registered
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: portmap query failed: RPC: Program not registered
mount.nfs: requested NFS version or transport protocol is not supported


RPC trouble?


Does anybody have any idea what happened here or how I can fix it?

Really tired. Going to bed now.

Thanks.

Mark

[mark9117]

Aaaaand I believe it may be fixed.

I found this: viewtopic.php?t=7411&p=47536

Based on info in that post, I stopped the unfs3 service and restarted nfs-server. I was then able to mount the shares in question with no errors.

I looked up unfs3 and understand that it provides user space, a daemon, mount and nfs protocols for some clients, but why did it show up on my server all of a sudden? Has it been there all along and just behaved itself until now?

I've disabled that service, but I don't know what I may be missing by doing so.

Any information welcome.

Thanks.