24.07.2016 05:13, Chris Murphy пишет:
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.
It does not say that it should continue to watch for device to appear and mount it months and probably years after user executed "mount -a".
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.
Seems unlikely that automatically mounting a degraded array is going to cause the array to be damaged. There's an event count that should serve to resolve any ambiguity which drive is newer than the other, although it might be better to make sure such md devices have a write-intent bitmap.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org