В Sun, 08 Dec 2013 14:34:02 +0100 "Carlos E. R." <robin.listas@telefonica.net> пишет:
On 2013-12-08 06:04, Cristian Rodríguez wrote:
/dev/disk/by-id/ata-ST2000DM001-1E6164_W1E4R7CL-part1 /data5 ext4 noatime,user,acl,user_xattr,nofail 1 2 /dev/disk/by-id/ata-ST2000DM001-1E6164_W1E4R7CL-part2 /data6 ext4 noatime,user,acl,user_xattr,nofail 1 2
set noauto in /data6 if you do not want systemd to mount it, otherwise it will do so, as expected.
Hey, no, it is expected they be mounted at boot, or when the admin uses "mount -a". It is not expected that they are mounted after the admin has umounted them manually.
No, this statement (taken "as is" without context) is incorrect. systemd will not mount filesystem "after the admin has umounted them manually". What happens here is - when filesystem is entered in /etc/fstab with "auto,nofail", systemd tries to mount this filesystem as soon as it sees device for it. Without "nofail" it would have failed on boot already. When filesystem is unmounted using GUI, device is deleted from system, so next time device appears it is attempted to be mounted. This behavior is rather unexpected to me as well and seems new in systemd coming with 13.1. I cannot say whether this is intentional change or not.