Bug#752104: systemd: tries to run fsck on a mounted filesystem

Michael Biebl biebl at debian.org
Mon Jun 23 23:14:35 BST 2014


forcemerge 751845 752104
thanks

Am 19.06.2014 18:18, schrieb Lionel Elie Mamane:
> Package: systemd
> Version: 204-8
> Severity: normal
> 
> Just switched to systemd (installed systemd-sysv), on an up-to-date
> jessie system.
> 
> On reboot, I notice:
> 
> Jun 19 17:53:02 fort systemd-fsck[959]: /dev/mapper/fort-root is mounted.
> Jun 19 17:53:02 fort systemd-fsck[959]: e2fsck: Cannot continue, aborting.
> Jun 19 17:53:02 fort systemd-fsck[959]: fsck failed with error code 8.
> Jun 19 17:53:02 fort systemd-fsck[959]: Ignoring error.
> 
> 
> AFAIK, it should run fsck with the root filesystem mounted read-only,
> this error message suggests the root filesystem was already mounted
> read/write.
> 
> Maybe linked to the root filesystem being an lvm logical volume.


Looks like a duplicate of #751845, so merging the two bug reports.

In both cases it seems to affects lvm volumes, so I wonder if that might
be relevant.




-- 
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: 884 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140624/3300d492/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list