On 2016-07-24 04:13, Chris Murphy wrote:
On Sat, Jul 23, 2016 at 7:51 PM, Carlos E. R. <> wrote:
On 2016-07-22 18:12, Istvan Gabor wrote:
There is another strange problem: ff I assemble an array it gets mounted automatically. Why? In case of a degraded array with one drive only this can ruin the array. Why is the array mounted automatically upon assembly? It should be only mounted (automatically) on running mount -a and at boot.
Systemd feature, I understand. If a disk is set to be automatically mounted by "mount -a" or boot, it will be mounted the instant the system sees it.
Something would be broken if it didn't work this way. 'man mount' says that -a mounts all file systems mentioned in fstab unless noauto is used. Since ancient times, as in I can't remember a time before this, it's true that anything in fstab is automatically mounted when the device appears and passes udev tests, unless noauto is used.
No, system V did not attempt to mount automatically a partition after boot. The time was past. So for many years we relied on this methodology. A device that appeared later had to be mounted by some other mechanism. Like calling "mount -a" again. Now systemd can umount automatically something that the admin mounted manually, or the other way round. It does not obey orders. -- Cheers / Saludos, Carlos E. R. (from openSUSE Leap 42.1 x86_64 (test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org