Con no longer mount an NFS volume

English Network/Internet
1

The NFS volume has mounted reliably for years. Now, not at all.

$ sudo mount -v /u
[sudo] password for root: 
mount.nfs: timeout set for Sat Nov 16 14:42:14 2019
mount.nfs: trying text-based options 'vers=4.2,addr=fd2f:4760:521f:3f3c::c0a8:45f6,clientaddr=fd2f:4760:521f:3f3c::c0a8:4573'
^C

Performing the above at the client produces 100s of error messages per second at the server. A sample of 2:

2019-11-16T14:40:17-0700 sma-server3 kernel: rpc-srv/tcp: nfsd: got error -95 when sending 28 bytes - shutting down socket
2019-11-16T14:40:17-0700 sma-server3 kernel: rpc-srv/tcp: nfsd: got error -95 when sending 28 bytes - shutting down socket

Any ideas what has gone awry?

2

Show us the pertinent mount entry please.

3 
sma-server3.sma.com:/data01/t-drv  /u   nfs    defaults  0  0
4

Also likely related to your networking issue I presume…?

5

Yes, indeed, the DHCP failure was the problem.
I configured another host to offer the DHCP service. And, Voila!, both NFS and SMB volumes mounted as expected.

The DHCP thread: https://forums.opensuse.org/showthre…ecided-to-quit

6

Then please post in those other two threads that they are solved and all concentrates now on the DHCP one. Because else people are still working on the other ones.