Am 07.12.2016 um 17:36 schrieb Daniel Pocock: > Control: tags -1 - moreinfo > > I've observed this problem again today > > Looking more closely, I noticed that it started to fsck the mount just > before it tried to mount it. It didn't appear to wait for fsck to finish: > > > > > Dec 03 10:51:37 systemd[1]: Started File System Check on > /dev/mapper/vg00-foo_host1_bak. > Dec 03 10:51:37 systemd[1]: > systemd-fsck@dev-mapper-vg00\x2dfoo_host1_bak.service: cgroup is empty > Dec 03 10:51:37 systemd[1]: Mounting /backup/host1/foo... > Dec 03 10:51:38 systemd[1]: About to execute: /bin/mount -n > /dev/mapper/vg00-foo_host1_bak /backup/host1/foo -t ext4 > Dec 03 10:51:38 systemd[1]: backup-host1-foo.mount changed dead -> mounting > Dec 03 10:51:38 systemd[1068]: Executing: /bin/mount -n > /dev/mapper/vg00-foo_host1_bak /backup/host1/foo -t ext4 > Dec 03 10:51:38 mount[1068]: mount: /dev/mapper/vg00-foo_host1_bak is > already mounted or /backup/host1/foo busy
Could you attach a systemd-analyze dump when you get such a failed boot. This way we should be able to see, if the fsck job is properly ordered or not. Is it always the same partition which fails? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
