Bug#829180: appears to be failing because of fsck

[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 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





More complete log attached

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2016-12-03-summary.log
Type: text/x-log
Size: 3668 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20161207/8298bb86/attachment-0001.bin>