[opensuse-factory] zypper dup umounts NFS shares
Hello, while updating to the latest Tumbleweed, a NFS share was umounted. This share is listed in /etc/fstab, but mounted manually ("noauto"). The symptoms look like the long-fixed https://bugzilla.opensuse.org/show_bug.cgi?id=880208 but I couldn't reproduce it by force-reinstalling the nfs-client and nfs-kernel-server packages. Unfortunately this happened while installing the "big" update with 4000 updated packages, which makes it hard to find out which package did this. It also makes it hard to report a bug - "one of these 4000 packages umounts NFS shares" isn't what developers want to see ;-) Any ideas which package could trigger the umount? Regards, Christian Boltz --
Und nun rate mal, warum ausgerechnet v.a. Vielschreiber mutt verwenden. Sicher nicht, weil KMail besser waere. Weil eine Handvoll muttschisten die alle dazu gezwungen hat? ;) [> David Haller und Manfred Misch in suse-linux]
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/01/2016 03:47 PM, Christian Boltz wrote:
while updating to the latest Tumbleweed, a NFS share was umounted. This share is listed in /etc/fstab, but mounted manually ("noauto").
No problem here. But I'm using "autofs". So it's possible that the share was umounted, and then autofs mounted it again.
Any ideas which package could trigger the umount?
Maybe a package for "wicked" or "NetworkManager" causes the network to be restarted. And since you have "noauto", the share would not be automatically mounted. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Christian Boltz -
Neil Rickert