On Sat, May 24, Cristian Rodríguez wrote:
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?
No, it is not. This is a system just running normally (at least, the sole user, me, is running normally)
A generator, man systemd-fstab-generator 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
ok, it is local-fs.target. I see both /var/run/systemd/generator/local-fs.target.wants/data5.mount and /run/systemd/generator/local-fs.target.wants/data5.mount (also for data6...) Does it help to remove those files from the local-f.target.wants directory? Michael -- Michael Fischer michael@visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org