On Thu, Feb 6, 2014 at 1:03 AM, Sébastien Leblanc <leblancsebas@xxxxxxxxx>wrote: > Conclusion (as I understand it): > > 1. There is definitely a bug in Journalctl: it crashes (segfaults) on I/O > errors. > > 2. You have a drive that is failing, or your BIOS might not be set > correctly. > Thanks, all, for the analysis. I have submitted a bug report [1] for systemd. Also, it seems you were right about hardware failure -- though I still can't get smartctl to acknowledge anything being wrong (except for nonzero current pending sector count), I ran badblocks, which found a bunch of errors, including on sectors corresponding to files outside /var/log/journal. Guess I should get a new drive. [1] https://bugs.freedesktop.org/show_bug.cgi?id=74714
