[Bug 1120087] New: NFS server fails after a suspend system
http://bugzilla.opensuse.org/show_bug.cgi?id=1120087 Bug ID: 1120087 Summary: NFS server fails after a suspend system Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: gerben.jansen@aol.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 Build Identifier: I have a laptop system that has in its /etc/exports file: /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) 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 then i suspend the server system with "systemctl suspend". When i next startup/resume 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. Reproducible: Always Steps to Reproduce: 1.On an NFS client, mount /MyLib 2.On that NFS client, unmount /MyLib again 3.Suspend the NFS server = do as root: systemctl suspend 4.Startup/resume the server 5.try step 1 Actual Results: step 5 fails with "mount.nfs: requested NFS version or transport protocol is not supported" rebooting the NFS client doesn't help, rebooting the server does. Expected Results: successful mount this is a regression from Leap 42.3, 42.2 and 42,1 where this scenario worked OK. 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 for my Leap systems. However i don't want to keep it running 24x7. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1120087 Gerben Jansen <gerben.jansen@aol.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1120087 http://bugzilla.opensuse.org/show_bug.cgi?id=1120087#c9 --- Comment #9 from Gerben Jansen <gerben.jansen@aol.com> --- Thanks for the update. I'm a bit put off by all the warnings in https://www.kernel.org/doc/html/v4.20/driver-api/usb/persist.html, i'm not going to use it since i'm pretty sure that sometime in the future (when i forgot about this issue) i'll get bitten by it. I would be a lot happier if nfsd did survive a file system unmount. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1120087 http://bugzilla.opensuse.org/show_bug.cgi?id=1120087#c11 --- Comment #11 from Gerben Jansen <gerben.jansen@aol.com> ---
I would be a lot happier if nfsd did survive a file system unmount. A proper solution for that will be a while in coming.
I think i'll opt just for rebooting the NFS server. I realize that a real fix is complex and (when the USB device is removed during the suspend period could cause problems. I was hoping that on going into suspense the file system could be sync'ed and coming out of suspense nfsd could detect that the file system still is there and continue to export it without getting the error on the client. Thanks anyway. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1120087 http://bugzilla.opensuse.org/show_bug.cgi?id=1120087#c12 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #12 from Neil Brown <nfbrown@suse.com> --- I don't think there is anymore more do to here, so closing. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com