"Cristian Rodríguez" írta:
El 24/05/14 19:07, Michael Fischer escribió:
2014-05-24 host systemd[1]: Unmounting /data5... 2014-05-24 host umount[20557]: umount: /data5: target is busy. 2014-05-24 host umount[20557]: (In some cases useful info about processes that use 2014-05-24 host umount[20557]: the device is found by lsof(8) or fuser(1)) 2014-05-24 host systemd[1]: data5.mount mount process exited, code=exited status=32 2014-05-24 host systemd[1]: Failed unmounting /data5.
That's part of a shutdown sequence right?
2014-05-24 host mtp-probe: checking bus 4, device 8: "/sys/devices/pci0000:00/0000:00:14.0/usb4/4-2" 2014-05-24 host mtp-probe: bus: 4, device: 8 was not an MTP device 2014-05-24 host systemd[1]: Found device ST2000DM001-1E6164. 2014-05-24 host systemd[1]: Found device ST2000DM001-1E6164. 2014-05-24 host systemd[1]: Starting File System Check on /dev/disk/by-id/ata-ST2000DM001-1E6164_W1E4R7CL-part2... 2014-05-24 host systemd-fsck[20587]: /dev/sde2: clean, 224834/54992896 files, 39120841/219942400 blocks 2014-05-24 host systemd[1]: Started File System Check on /dev/disk/by-id/ata-ST2000DM001-1E6164_W1E4R7CL-part2. 2014-05-24 host systemd[1]: Mounting /data6... 2014-05-24 host systemd[1]: Mounted /data6.
/data5 and /data6 should not be getting mounted by anything other than me, as I understand it. This behavior screws up programs sourcing files on those partitions.
Or is 'noauto' only about boot time (man page suggests such)?
What systemd service is doing this?
A generator, man systemd-fstab-generator
Mounting a file system if noauto is specified is a serious bug. An unwanted mount may destroy data on the file system. No application should touch such file system. I had similar experience with gnome (file manager?) earlier, it also mounted file sytems marked noauto. There is a reason why it is marked noauto and the system (even being systemd god) should not disregard it.
How is it launched? And is there a better way
to tell systemd to stop this behavior on those partitions?
Reading the code of the generator, if you remove "nofail" it will do what you want.
noauto --> mount will not be added as a dependency for local-fs.target
nofail --> mount will be only wanted, not required, by local-fs.target
How can a mount be a dependency? This is stupid. 1. Should files be located on the given file system systemd should give error message, not override the administrator's setting. 2. systemd should stick to conventional behavior. 3 You cannot expect a user to read systemd code generator (I even don't know what it is). I think systemd developers should change they program so that it does not touch noauto marked file systems. Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org