x-posted to factory, as this is 13.2 behavior... Carlos E. R. wrote:
On 2014-10-24 21:57, Ruediger Meier wrote:
So what kind of automount is this? How to disable this odd behaviour? Is this a known bug?
Yes.
Um... this sounds like a different bug than the one you mention below. The previous discussion that you quote had auto-remounting happen despite inclusion of "noauto". Now it "only" happens in situations that should ***NEVER*** occur unless someone (or something -- like a kernel) with administrative privileges has manually unmounted. If that's the case --- then something automounting it again is horrible problem -- if there was file corruption causing the unmount, or if suspected file corruption causes an admin to unmount a file system, having a something in the background try to auto-remount such an file system could cause a severe increase of corruption -- not just on that file system, but on the system as a whole -- where it could very easily crash the system. I.e. if a file system that was set for auto-mounting at boot is found to be "unmounted", than any attempt to mount it is "glossing over" the reason why the file system became unmounted in the first place and quite possibly contributing to its corruption or, in worst case, loss of the data on the file system. >>>>>>>>>> /etc/fstab != /etc/auto.xxx... <<<<<<<<<<<<<
Date: Sat, 24 May 2014 19:07:18 -0400 From: Michael Fischer <> To: opensuse@opensuse.org Subject: [opensuse] Why is systemd[1] is mounting noauto partitions?
You participated in that thread :-)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org