Bug#754340: Unable to run fsck manually when instructed to do so

[Michael Biebl]

Am 12.07.2014 00:34, schrieb Bas Wijnen:
> When fsck failed with this message before, I could do:
> mount / -o remount,ro
> fsck /
> 
> Now, and I'm guessing this is a change on the part of systemd, that
> first command (remount read-only) fails with the message that the file
> system is busy.  Having no bootable computer and thus no internet, I was
> unable to figure out what was keeping it busy, and how I was supposed to
> stop it.  This is the information that I think should be part of the
> "please run fsck manually"-message, because that won't work without it.

I think there is no general answer to that.
There most likely simply was a process keeping your (root) fs busy.
So I would have tried stopping one service after another.

Do you have a /var/log/journal/ directory and is this on the root
directory? Might be that journald kept your fs busy.

Michael


-- 
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/20140712/ae1881e7/attachment-0002.sig>