NFS mount problem

English Network/Internet
1

Hello,

I have a NIS/NFS client that was running OpenSUSE 13.2v. Last week I upgrade (using network upgrade steps) to Tumbleweed.

Now I can not mount the NFS shares. The NIS server is working ok.

Some messages:

lamodel:~ # systemctl status nfs.service
● nfs.service - Alias for NFS client
   Loaded: loaded (/usr/lib/systemd/system/nfs.service; enabled; vendor preset: disabled)
  Drop-In: /run/systemd/generator/nfs.service.d
           └─50-insserv.conf-$remote_fs.conf
   Active: failed (Result: exit-code) since Thu 2016-02-18 17:45:06 BRST; 16h ago
  Process: 8973 ExecStop=/usr/bin/umount -aft nfs,nfs4 (code=exited, status=0/SUCCESS)
  Process: 8966 ExecStartPost=/usr/bin/mount -at nfs,nfs4 (code=exited, status=32)
  Process: 8963 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
 Main PID: 8963 (code=exited, status=0/SUCCESS)

Feb 18 17:45:06 lamodel systemd[1]: Starting Alias for NFS client...
Feb 18 17:45:06 lamodel mount[8966]: mount.nfs4: mount system call failed
Feb 18 17:45:06 lamodel systemd[1]: nfs.service: Control process exited, code=exited status=32
Feb 18 17:45:06 lamodel systemd[1]: Failed to start Alias for NFS client.
Feb 18 17:45:06 lamodel systemd[1]: nfs.service: Unit entered failed state.
Feb 18 17:45:06 lamodel systemd[1]: nfs.service: Failed with result 'exit-code'.

lamodel:~ # showmount -e chem-alpha
Export list for chem-alpha:
/home 172.16.40.0/255.255.0.0

(chem-alpha is the NIS/NFS server)

lamodel:~ # mount -a
mount.nfs: mount system call failed

The input in fstab:

chem-alpha:/home        /home   nfs     defaults 0 0

Also: rpcbind is running normally and I am not using NetworkManager.

Any ideas?

Thanks in advance

2

I don’t have anything to suggest.

I’m posting, only to indicate that NFS is working fine for me.

I did update Tumbleweed yesterday (to snapshot 20160212). I did not think to check NFS after that. So I rebooted this morning. And NFS is doing fine.

In my case, I am using “autofs” for mounting. The autofs-mounted directory is still mounting on demand. It is mounted from a different box (from my desktop running Leap 42.1).

I don’t know if there has been a change from 13.2 to Tumbleweed that would account for your problem. If there was such a change, then “autofs” seems to have changed so as to keep everything working.

3

Hello,

I added this

rw,hard,intr,nolock,nfsvers=3  0  0

to my fstab together with the IP instead the server name and now everything is working ok, my NFS shares are mounted at boot.

4

This suggests name resolution issues.
Although you’ve found a workaround, unless you solve any name resolution issues you may see related problems in the future.

TSU

5

hatuey,

I agree with tsu2 it is a name resolution problem. I always use IP’s for NFS mounts. Since I have one computer serving out host info, the remotes can not rely on NSS_LDAP starting fast enough to resolve host names during boot.

Dave W

6

Sure, but this problem only appear AFTER the upgrade to Tumbleweed. the v13.2 was working ok.

Thank you both for your comments.