On 15/12/16 00:29, Michael Biebl wrote: > Am 07.12.2016 um 17:36 schrieb Daniel Pocock: >> 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: > > Fwiw, the log you provided doesn't seem to confirm that. > > mount for /dev/mapper/vg00-foo_host1_bak is only done after the > fsck has completed > (systemd-fsck@dev-mapper-vg00\x2dfoo_host1_bak.service: main > process exited, code=exited, status=0/SUCCESS) >
Please look more closely ... 3 lines after that it says the fsck has "Started" and then it gives another line about "cgroup is empty" Could that just be a fault with re-ordering the log entries in journald? Or maybe it is starting fsck twice? Regards, Daniel
