I have a server system that has in its /etc/exports file:[FONT=courier new]/MyLib 192.168.2.0/24(fsid=0,crossmnt,rw,no_root_squash,async,no_subtree_check,insecure)
/MyDisk 192.168.2.0/24(fsid=1,crossmnt,rw,no_root_squash,async,no_subtree_check,insecure)
[/FONT]
I can mount these from a NFS client without issues.
In the /etc/fstab I have on the client
server:/MyLib /MyLib nfs noauto,user 0 0
server:/MyDisk /MyDisk nfs noauto,user 0 0
Next i unmount the file systems on the client and next i suspend the server system with “sysctl suspend”.
When i next startup the server again I can no longer mount the file systems. Mount fails with:mount.nfs: requested NFS version or transport protocol is not supported
Rebooting the nfs client doesn’t help. Only a reboot of the server make the error go away.
Both the server and the client are running Leap 15 and are at the latest patches (17 Dec 2018)
Before, when i was running Leap 42.3 on both, this worked OK.
I do not think it is a good idea to suspend an NFS server. IMHO NFS was never designed with such an event in mind. It was invented for Unix systems when something like a desktop (let alone laptop) type of computer did not exist. I do not know much about the internals of NFS, but I can easily understand that an interruption of the working of the processes on the server can create havoc.
Only thing is that you report that 42.3 did what you wanted. I then can advise is to report a bug because of loss of functionality. You can find how to do that at: https://en.opensuse.org/openSUSE:Submitting_bug_reports
Use the same username/password as here.
BTW, as you are new here, we have an important message ;):
There is an important, but not easy to find feature on the forums.
Please in the future use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.
First, an “Amen’ to any idea about suspending or hibernating or anything else similar on a NFS server, the simple answer is 'Don’t.” The server should be at least shut down when it’s not running, and booted back up when you want the server available.
Besides that,
sysctl commands should be considered deprecated on today’s systemd architecture.
Although the commands might work, their true effect would be unknown since those commands should generally be replaced with others (primarily systemctl commands). Exceptions might be where you explicitly reference something in /etc/sysctl.conf.
You may want to skim the LEAP documentation to update your understanding of NFS (following link) and other things in today’s openSUSE (which is not different than most other Linux distros as well, almost all major distros have evolved greatly the last 5 years or so)
I agree your argument about not suspending an NFS server. However at the moment of suspend no NFS client has anything mounted, so in my eyes there should be nothing active on the NFS server, just NFS servers waiting for someone.
As far as I know NFS is stateless and if all clients have disappeared there should be nothing left active/open on the server.
I run NFS services on an old laptop and use it to serve out movies/pictures to a Minix player. I also use it as a backup server. However i don’t want to keep it running 24x7.
Up to version 42.3 suspending it wasn’t a problem.