Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#36467 - journald logs get corrupted too easily

Attached to Project: Arch Linux
Opened by Juan Luis (heavymetal) - Thursday, 08 August 2013, 23:03 GMT
Last edited by Dave Reisner (falconindy) - Friday, 23 August 2013, 01:24 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Running as root `journalctl --verify` in my machine shows tons of errors even though I have never turn off the computer in a bad way since the last time I wiped all my logs (although I needed to kill X server a couple of times). The last time I wiped all my logs was because they were corrupt too. I have this issue both in my desktop, with LVM, and in my laptop, without LVM. Almost every user of Arch Linux I told to try this command suffers the same issue. It has also been shortly discussed on the forum. https://bbs.archlinux.org/viewtopic.php?id=163645

These corruptions cause journalctl to malfunction, i.e. in some case it can enter in a loop not being able to reach last logs.

Additional info:
* systemd version: 204

Steps to reproduce:
1. journalctl --verify
2. Oh! Yours are corrupt too!

Screenshot: http://i.imgur.com/fbbCb21.png
This task depends upon

Closed by  Dave Reisner (falconindy)
Friday, 23 August 2013, 01:24 GMT
Reason for closing:  Upstream
Additional comments about closing:  Not a packaging bug. Take it up with systemd upstream.
Comment by Nekmo (nekmo) - Friday, 09 August 2013, 00:22 GMT
My Journal's corrupt too.

http://share.nekmo.com/homura_desktop72.png
Comment by Dave Reisner (falconindy) - Friday, 09 August 2013, 01:52 GMT
Seems weird to be wiping logs that are still readable. More likely the verification logic has issues, not your journal files (they're append-only, making corruption extremely difficult).

Report it upstream if there isn't something existent already. Nothing for Arch to do.

Loading...