Here are some details. fstab line : LABEL=Data /data ext4 nofail,auto 0 1
journalctl -b | grep Data : Jul 17 04:24:21 mickael-laptop systemd[1]: Expecting device dev-disk-by\x2dlabel-Data.device... Jul 17 04:25:51 mickael-laptop systemd[1]: Job dev-disk-by\x2dlabel-Data.device/start timed out. Jul 17 04:25:51 mickael-laptop systemd[1]: Timed out waiting for device dev-disk-by\x2dlabel-Data.device. Jul 17 04:25:51 mickael-laptop systemd[1]: Dependency failed for File System Check on /dev/disk/by-label/Data. systemctl list-jobs (before timeout) : JOB UNIT TYPE STATE 11 data.mount start waiting 12 systemd-fsck@dev-disk-by\x2dlabel-Data.service start waiting 13 dev-disk-by\x2dlabel-Data.device start running When shutting down, the message "A start job is running for dev-disk-by\x2dlabel-Data.device" shows up and I have to wait for the timeout to end. For now, a workaround I found is to change "auto" to "noauto" and symlink dev-disk-by\\x2dlabel-Data.device.wants/data.mount to /run/systemd/generator/data.mount Disabling the file-system check also seems to fix the issue (discovered that just now) 2013/7/17 Lennart Poettering <lenn...@poettering.net>: > On Sun, 16.06.13 22:32, Mickaël THOMAS (micka...@gmail.com) wrote: > >> >> I've also found another issue regarding this (it's a small issue but >> still...) >> >> Using "nofail" (and implied "auto") works as expected but if the >> device is not there at boot time, systemd will try to mount it anyway >> and fail after a certain timeout. >> Problem is, if I happen to shutdown my machine before the timeout >> ends, it will hang until the timeout has passed. >> Ideally, I don't need systemd to try to mount the device if the disk >> isn't there. Perhaps this could be the behavior when "nofail" option >> is used. >> >> What's your thoughts about this? > > Oh, umm. So "nofail" is not supposed to cause delays at boot > really. This really should just mount the fs if it is found during > early-boot. If it isn't found it shouldn't get mounted or anything > delayed for it. > > if this causes a delay for you then there's a bug somewhere. > > What's the precise fstab line you use now? > > Lennart > > -- > Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel