Bug#829180: appears to be failing because of fsck

[Michael Biebl]

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 at dev-mapper-vg00\x2dfoo_host1_bak.service: main
process exited, code=exited, status=0/SUCCESS)

> 
> 2016-12-03-summary.log
> 
> 
> Dec 03 10:51:32 systemd[1]: Installed new job backup-host1-foo.mount/start as 58
> Dec 03 10:51:32 systemd[1]: Installed new job dev-mapper-vg00\x2dfoo_host1_bak.device/start as 59
> Dec 03 10:51:32 systemd[1]: Installed new job systemd-fsck at dev-mapper-vg00\x2dfoo_host1_bak.service/start as 60
> Dec 03 10:51:32 systemd[1]: Expecting device dev-mapper-vg00\x2dfoo_host1_bak.device...
> Dec 03 10:51:36 systemd[1]: dev-vg00-foo_host1_bak.device changed dead -> plugged
> Dec 03 10:51:36 systemd[1]: dev-mapper-vg00\x2dfoo_host1_bak.device changed dead -> plugged
> Dec 03 10:51:36 systemd[1]: Job dev-mapper-vg00\x2dfoo_host1_bak.device/start finished, result=done
> Dec 03 10:51:36 systemd[1]: Found device /dev/mapper/vg00-foo_host1_bak.
> Dec 03 10:51:36 systemd[1]: dev-disk-by\x2did-dm\x2dname\x2dvg00\x2dfoo_host1_bak.device changed dead -> plugged
> Dec 03 10:51:36 systemd[1]: Starting File System Check on /dev/mapper/vg00-foo_host1_bak...
> Dec 03 10:51:36 systemd[1]: About to execute: /lib/systemd/systemd-fsck /dev/mapper/vg00-foo_host1_bak
> Dec 03 10:51:36 systemd[1]: systemd-fsck at dev-mapper-vg00\x2dfoo_host1_bak.service changed dead -> start
> Dec 03 10:51:36 systemd[935]: Executing: /lib/systemd/systemd-fsck /dev/mapper/vg00-foo_host1_bak
> Dec 03 10:51:37 systemd-fsck[935]: /dev/mapper/vg00-foo_host1_bak: clean, 269/2293760 files, 8636385/9175040 blocks
> Dec 03 10:51:37 systemd[1]: Child 935 belongs to systemd-fsck at dev-mapper-vg00\x2dfoo_host1_bak.service
> Dec 03 10:51:37 systemd[1]: systemd-fsck at dev-mapper-vg00\x2dfoo_host1_bak.service: main process exited, code=exited, status=0/SUCCESS
> Dec 03 10:51:37 systemd[1]: systemd-fsck at dev-mapper-vg00\x2dfoo_host1_bak.service changed start -> exited
> Dec 03 10:51:37 systemd[1]: Job systemd-fsck at dev-mapper-vg00\x2dfoo_host1_bak.service/start finished, result=done
> 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 at 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


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20161215/3712d7d0/attachment-0002.sig>