[Bug 964347] New: NFS shares unmounted after suspend/resume
http://bugzilla.suse.com/show_bug.cgi?id=964347 Bug ID: 964347 Summary: NFS shares unmounted after suspend/resume Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: darren@freemaninstruments.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I've recently gone from 13.2 to Tumbleweed. I have a remote NFS share mounted on this laptop. Now, when I suspend and resume, the NFS share is unmounted. I have to manually mount it every time, from a root shell. The relevant line in /etc/fstab: server:/data /data nfs4 defaults,noauto,nofail 0 0 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c1
--- Comment #1 from Darren Freeman
http://bugzilla.suse.com/show_bug.cgi?id=964347
Chenzi Cao
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c2
Neil Brown
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c3
--- Comment #3 from Darren Freeman
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c4
Darren Freeman
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c5
Neil Brown
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c6
--- Comment #6 from Neil Brown
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c7
--- Comment #7 from Neil Brown
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c8
--- Comment #8 from Darren Freeman
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c9
--- Comment #9 from Darren Freeman
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c10
--- Comment #10 from Darren Freeman
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c11
Neil Brown
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c12
Darren Freeman
I'm guessing that /usr/bin/systemctl is-enabled nfs.service reports "diabled".
True.
Can you run systemctl enable nfs.service
and see if that changes things?
I just tested it once by suspending and resuming.. and the NFS share is still mounted! Hooray!! So what does that tell us.. I would have added the entry to /etc/fstab manually by copying it from my old laptop. It mounts successfully upon initial boot-up, so I would have assumed it was done. I don't recall seeing any documentation that told me to run the above command. As I'm not running an NFS server, I would have assumed that I don't need to do this if I were casually looking at the state of all the services. Should one of the config tools (i.e. YaST) notice when there is an NFS mount in /etc/fstab, and enable the service? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c13
Neil Brown
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c14
--- Comment #14 from Darren Freeman
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c15
--- Comment #15 from Neil Brown
So if there are going to be some user-space tools...
There is. Use automount. Really, it isn't very hard and worth all the effort it takes. Make sure you have "autofs" installed. Create a file "/etc/auto.master.d/direct.autofs" containing one line /- /etc/auto.direct Then create /etc/auto.direct containing one line for everything you want NFS mounted. e.g. /scratch -fstype=nfs,vers=4 my-big-servier:/scratch /otherhome -fstype=nfs desktop:/home and "systemctl reload autofs" and you are done. Nothing more to worry about. They only get mounted when you try to access them, and if the mount fails, you get a small delay then 'file not found'. They get unmounted after a short period of inactivity (configurable). Apps will only freeze if they "cd" into the mounted directory or open a file in there and hold it open. If they use full pathnames get to get everything (which most apps seem to these days) they should simply fail when the filesystem cannot be mounted. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964347
http://bugzilla.suse.com/show_bug.cgi?id=964347#c16
Neil Brown
participants (1)
-
bugzilla_noreply@novell.com