First of all Journal is a logging system and is part of
systemd. Their existence is crucial when you need to know what happened.
As mentioned here,
journalctl --file isn't that usable.
As the journal files are rotated periodically, this form is not really usable for viewing complete journals.
Now, whether you consider the files useless, that's for you to decide. Normally, too old logs are not worth keeping and you could delete them.
To do that, is best to use
journalctl itself and its utility vacuum. For instance you can use
sudo journalctl --vacuum-time=3weeks
to delete all journal files that are more than 3 weeks old.
For more info check the man page with
--vacuum-size=, --vacuum-time=, --vacuum-files=
Removes the oldest archived journal files until the disk space they
use falls below the specified size (specified with the usual "K", "M",
"G" and "T" suffixes), or all archived journal files contain no data
older than the specified timespan (specified with the usual "s", "m",
"h", "days", "months", "weeks" and "years" suffixes), or no more than
the specified number of separate journal files remain. Note that
running --vacuum-size= has only an indirect effect on the output shown
by --disk-usage, as the latter includes active journal files, while
the vacuuming operation only operates on archived journal files.
Similarly, --vacuum-files= might not actually reduce the number of
journal files to below the specified number, as it will not remove
active journal files.
Also, I don't believe its worthwhile to periodically check this. Best thing you can do is set an upper limit by uncommenting and changing the following in
Then restart the service.
sudo systemctl restart systemd-journald.
man journald.conf for more information.
As explained by @reinierpost
This question is not about regular old logs, it is about old logfiles
that do not appear to contain any logs at all (but they still occupy 8
journalctl --verify. If files don't pass then the journal is corrupted and you should restart the service.
sudo systemctl restart systemd-journald
That should fix the problem for logs going forward.
As for why this happened in the first place, I don't know and its not easy to figure out. And yes, corrupted files are probably junk. You could try this for a clean slate.