Bug#751486: systemd: journald flooding logs if filesystem is mounted read-only

[Michael Biebl]

Am 13.06.2014 14:35, schrieb Salvo Tomaselli:
> Package: systemd
> Version: 204-10
> Severity: normal
> 
> Dear Maintainer,
> 
> due to some filesystem problems, everything on my system except for /home, was
> mounted as read-only.
> This caused journald to flood me with error messages, preventing me from
> realizing what was actually going on. All I could see on the screen were
> journald error messages.
> 

Those error messages look correct to me, and I don't see what's unclear
about:
[   16.641908] systemd-journald[144]: Failed to write entry, ignoring:
Read-only file system

That exactly says that the file system is read-only, i.e. it is telling
you exactly what the problem is.

Silently ignoring the fact that the journal could not be written seems
the much worse alternative.

The systemd/journald behavior seems correct in this case.

Please elaborate where you see a bug in journald.

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/20140627/ecde9531/attachment-0002.sig>