<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [220] [journalctl] fails to open journal files"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90815">90815</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[220] [journalctl] fails to open journal files
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>bluewind@xinu.at
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>My computer crashed and afterwards I was unable to read my journal. journalctl
returns the following error and no log entries:
Error was encountered while opening journal files: No data available
I was also unable to run other journalctl commands like --disk-usage --verify
or --list-boots. I downgraded to 219 and was able to read my journal again and
bisected the issue to 7b300be75e6d5755778dd7da63e7147866f21351 (sd-journal:
return error when we cannot open a file).
journalctl --verify (from 219) tells me that I have some corruption. The 3
files mentioned are timestamped May 1 2015, Jul 14 2014, Jun 2 2015.
444188: invalid object
File corruption detected at
/var/log/journal/889479b0ab6d255dc4b25c5448fb1d0f/<a href="mailto:system@00051500f404eedd-1ca9f54ada114353.journal">system@00051500f404eedd-1ca9f54ada114353.journal</a>~:444188
(of 8388608 bytes, 53%).
000098: entry number mismatch
File corruption detected at
/var/log/journal/889479b0ab6d255dc4b25c5448fb1d0f/<a href="mailto:system@1f4ac564b53b45429a68bed9bd4d66b9-00000000000df3c5-0004fdff4b8778af.journal">system@1f4ac564b53b45429a68bed9bd4d66b9-00000000000df3c5-0004fdff4b8778af.journal</a>:000000
(of 8388608 bytes, 0%).
8c4000: invalid object
File corruption detected at
/var/log/journal/889479b0ab6d255dc4b25c5448fb1d0f/<a href="mailto:system@00051784997e6452-430d86854332cfc4.journal">system@00051784997e6452-430d86854332cfc4.journal</a>~:8c4000
(of 16777216 bytes, 54%).
I have not tested if journalctl from 220 actually worked before the crash.
Is this a bug or is this an expected outcome of the mentioned patch?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>