[Bug 341647] New: mounted nfs share does not show up after reconnect with k network manager
https://bugzilla.novell.com/show_bug.cgi?id=341647 Summary: mounted nfs share does not show up after reconnect with k network manager Product: openSUSE 10.3 Version: Final Platform: 32bit OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: reitenbach@rapideye.de QAContact: qa@suse.de Found By: --- when I login into the notebook, networkmanager enabled, and then open a konsole and enter mount, the nfs share is shown. When I then reconnect the network via knetworkmanager, then when it is ready, the mounted share is not shown anymore in the output of hte mount command. Well, it is still mounted where it was, and still listed in /proc/mounts, but not in /etc/mtab nor does it show up in the output of df. Expected behaviour: as long as the nfs share is mounted, it should show up in the mount command, and in df and in /etc/mtab, as all the other filesystems do. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341647 Mark Gordon <mtgordon@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mtgordon@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |hschaa@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341647#c1 Helmut Schaa <hschaa@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hschaa@novell.com AssignedTo|hschaa@novell.com |tambet@novell.com --- Comment #1 from Helmut Schaa <hschaa@novell.com> 2007-11-16 02:10:19 MST --- Seems to me like a NetworkManager-related bug. => Reassigning to Tambet -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341647 Tambet Ingo <tambet@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341647 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c2 Tambet Ingo <tambet@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|tambet@novell.com |nfbrown@novell.com --- Comment #2 from Tambet Ingo <tambet@novell.com> 2008-11-17 07:42:36 MST --- It does not matter how a network device is deactivated and NetworkManager does not write the content of /etc/mtab. Not sure who should be the assignee, please reassign if I got it wrong. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341647 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c3 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tambet@novell.com Status|NEW |NEEDINFO Info Provider| |reitenbach@rapideye.de --- Comment #3 from Neil Brown <nfbrown@novell.com> 2008-11-17 13:55:12 MST --- Could I get some more details please. 1/ how is the nfs share mounted? via fstab or automount? If fstab, what is the exact line from fstab. 2/ Can you ask knetworkmanager to disconnect the network rather, then reconnect the network as two separate steps. What is the state of the nfs share where the network is disconnected? 3/ after the reconnect, you say the share is still mounted. Can you still successfully access the filesystem 4/ Please attach any content from /var/log/messages for a couple of minutes before the reconnect to a couple of minutes after I believe that the preferred behaviour for network manager is to unmount any nfs share when the network is disconnected, and remount anything in /etc/fstab when the network is connected. Tambet: Is this how it is supposed to work? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341647 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c4 --- Comment #4 from Tambet Ingo <tambet@novell.com> 2008-11-18 00:17:18 MST --- By default, the NFS mount notification from NM is pretty weak, see /etc/NetworkManager/dispatcher.d/nfs The comment "It is too late to stop NFS. Better to do nothing..." means that the dispatcher scripts are executed when the device has lost the connection already. In many cases, it's simply not possible to do it in the right time - wifi is not very reliable, ethernet cable could be pulled off from a laptop any moment, on suspend there's simply not enough time, especially since a (bad) script could take a long time to finish, etc. I personally usually have custom NM dispatcher scripts that look at the properties of the connection to see what shares to mount and use 'soft' option to make it possible to unmount after the connection has already been lost. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341647 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c5 --- Comment #5 from Neil Brown <nfbrown@novell.com> 2008-11-20 19:52:06 MST --- If the network has gone away it is still quite possible to do a lazy unmount: umount -alt nfs,nfs4 If any processes are actively using the mountpoints they will block if they every try to access anything, but new processes that try to touch things will get a simple "file not found" until the link comes back up and the nfs filesystems are remounted. If the IP address has changed, it is important to remove the old mount and create a new mount as the old mount will very likely hang even though the network is back. Would it be possible to change dispatcher.d/nfs to do that? It isn't suitable to do "/etc/init.d/nfs stop" as that currently isn't safe if the network is gone. Just an explicit "umount -alt nfs,nfs4" would be best. Sebastian: is it possible to get answers to Comment #4 ?? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341647 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c6 --- Comment #6 from Tambet Ingo <tambet@novell.com> 2008-11-21 00:27:10 MST --- Ok, thanks for the suggestion, will do that for b6/rc1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341647 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c7 --- Comment #7 from Tambet Ingo <tambet@novell.com> 2008-11-21 06:05:33 MST --- "umount -alt nfs,nfs4" is executed from NetworkManager dispatcher script now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341647 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c8 --- Comment #8 from Neil Brown <nfbrown@novell.com> 2008-12-04 15:41:19 MST --- Hi Sebastian, We still need the information requested in comment #4 to proceed with this. If I don't here anything in another week I'll have to close the bug. Thanks.. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341647 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c9 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|reitenbach@rapideye.de | Resolution| |NORESPONSE --- Comment #9 from Neil Brown <nfbrown@novell.com> 2008-12-12 14:21:20 MST --- Closing due to lack of response. Please reopen if new information becomes available. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341647 User jnelson-suse@jamponi.net added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c10 Jon Nelson <jnelson-suse@jamponi.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |jnelson-suse@jamponi.net Resolution|NORESPONSE | --- Comment #10 from Jon Nelson <jnelson-suse@jamponi.net> 2009-03-20 10:38:05 MST --- This seems to have caused some problems for me. Specifically, it would appear that it is ignoring the configuration in /etc/sysconfig/network/config (including but not limited to CONNECTION_UMOUNT_NFS_BEFORE_IFDOWN) Furthermore, /etc/NetworkManager/dispatcher.d/nfs arbitrarily restarts nfs which is also not necessarily appropriate - specifically, /etc/init.d/nfs is not the only way in which nfs mounts can be made - those made by hand are then destroyed and not repaired (a brief blip or reconnect *to the same network* causes nfs mounts to be destroyed). I use the ifservices mechanism to mount via NFS certain directories based upon which network I am in. Since /etc/NetworkManager/dispatcher.d/nfs runs *after* the ifservices hook those mounts are unmounted!! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341647 User jnelson-suse@jamponi.net added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c11 --- Comment #11 from Jon Nelson <jnelson-suse@jamponi.net> 2009-03-20 10:38:55 MST --- I forgot to say that this is with opensuse 11.1 which is when the change to the netcontrol script went in (*after* 11.1 was released....) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341647 User nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c12 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nfbrown@novell.com AssignedTo|nfbrown@novell.com |tambet@novell.com --- Comment #12 from Neil Brown <nfbrown@novell.com> 2009-03-22 19:56:05 MST --- It sounds like most of the problem you describe is related to the network manager side, so I'm going to re-assign this to Tambet. The fact that hand-mounted NFS filesystems are dropped and not restored is unfortunate, but I don't think it is clear that there is a "right" answer for that. We could only unmount filesystems listed in /etc/fstab, but there would be situations where that wouldn't work as well. Having ifservices mount what you want should be able to be made to work I expect. Tambet - what do you think? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341647 User tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c13 Tambet Ingo <tambet@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #13 from Tambet Ingo <tambet@novell.com> 2009-03-23 00:50:27 MST --- First of all, when you use NetworkManager, you can forget about /etc/sysconfig/network/* configuration files. NM has it's own (cross distro) system which doesn't match in many places with suse configuration, so it was decided it's easier for everybody if the answer is "no", rather than "depends". For re-mounting services not listed in /etc/fstab, you'll need to write a dispatcher script for it yourself. The current dispatcher script is generic with a single rule: "when a device is activated, mount all NFS services". That doesn't take account movable devices (like laptops) where you can get connected anywhere and thus might not have access to the network resources (like NFS, ..) of your home/office. NM provides a way to solve that (by giving extra information to the dispatcher scripts), but there are currently no tools that use it. The rules ideally need to be like "if a specific configuration is activated/deactivated, do ...", which requires user configuration and right now, there are no graphical tools to configure that. A comment for "a brief blip or reconnect *to the same network* causes nfs mounts to be destroyed" - The dispatcher script runs right after disconnect - at which point, there is no way of knowing whether you'll get a connection back (to the same network or not) right away, so it's working as designed. In summary, I'm going to close this bug again - I don't think it would be a good default to try to remount NFS services which do not appear in /etc/fstab. I don't think it's what most people would want and we have infrastructure to override that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com