summaryrefslogtreecommitdiff
path: root/src/udev
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2013-06-22 20:04:08 -0400
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2013-06-22 20:36:01 -0400
commit92fba83e3a23ce7778a1bde67d277fdc97ab39f9 (patch)
tree9ca5de9e92835ea45a4e2d949d995aeb1095b5c6 /src/udev
parentfb69ed55e5f8e82145440ba15075e8db807bf7fa (diff)
journal-verify: allow unlinked data entries
Sometimes an entry is not successfully written, and we end up with data items which are "unlinked", not connected to, and not used by any entry. This will usually happen when we write to write a core dump, and the initial small data fields are written successfully, but the huge COREDUMP= field is not written. This situation is hard to avoid, but the results are mostly harmless. Thus only warn about unused data items. Also, be more verbose about why journal files failed verification. This should help diagnose journal failure modes without resorting to a hexadecimal editor. https://bugs.freedesktop.org/show_bug.cgi?id=65235 (esp. see system.journal attached to the bug report).
Diffstat (limited to 'src/udev')
0 files changed, 0 insertions, 0 deletions