Bug#801860: /bin/journalctl: journalctl --list-boots is too slow and memory hungry

[Michael Biebl]

Am 15.10.2015 um 14:43 schrieb Edward Allcutt:
>> How big is your /var/log/journal/ ? Is that on HDD or SSD?
>> What does "journalctl --verify" say?
> 
> It's a laptop spinning (at 7200 rpm) rust type storage device. I don't
> think speed of retrieval from the disk is a factor though.

seeking time might be.

> # journalctl --disk-usage
> Archived and active journals take up 144.0M on disk.
> # du -xsh /var/log/journal/
> 145M    /var/log/journal/
> # journalctl --verify
> PASS:
> /var/log/journal/2e7a303bb598373e73b04ccb5176b123/system at 917974e30b5f49e789deec21ee0c033f-0000000000000001-0005203f0834a00a.journal

...

Ok, that looks fine. 145M is also not a lot.
I do have 2G of journal data here (on SSD) though, and --list-boots is
instantaneous. (Shows about 220 boots).

Can you move /var/log/journal away for testing purposes (don't delete
the journal files!) and create a fresh /var/log/journal directory.
Then do a couple of reboots. Is the speed reasonable then?
Maybe there is something specific about those journal files which break
journalctl. In that case, would you be willing to share those journal files?

It's probably best if you file this issue upstream
https://github.com/systemd/systemd/issues







-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151015/2fb0ad47/attachment-0002.sig>