https://bugzilla.novell.com/show_bug.cgi?id=341647 Mark Gordon 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 Tambet Ingo 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 nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c3 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tambet@novell.com Status|NEW |NEEDINFO Info Provider| |reitenbach@rapideye.de --- Comment #3 from Neil Brown 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 nfbrown@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c5 --- Comment #5 from Neil Brown 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#c7 --- Comment #7 from Tambet Ingo 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#c9 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|reitenbach@rapideye.de | Resolution| |NORESPONSE --- Comment #9 from Neil Brown 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#c11 --- Comment #11 from Jon Nelson 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 tambet@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=341647#c13 Tambet Ingo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #13 from Tambet Ingo 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.