[systemd-devel] list-boots is incorrect, was: lost journal persistence

[Chris Murphy]

On May 12, 2014, at 7:06 AM, Kirill Elagin <kirelagin at gmail.com> wrote:

> Could it be that all the boot ids are actually the same for some reason?
> I had this issue in a container when systemd was reading boot_id from `/proc/sys/kernel/random/boot_id` and since /proc was bind-mounted, boot_id always was host's boot_id.
> 
> You can also run `journalctl -F _BOOT_ID` to see a set of all the boot ids recorded in the journal (this must agree with `journalctl --list-boots`.


# journalctl --list-boots | wc -l
36
[root at rawhide ~]# journalctl -F _BOOT_ID | wc -l
80
# cat /proc/sys/kernel/random/boot_id
420fa190-e7dd-4cd7-b248-fd62417d7c02
# reboot
###
# journalctl --list-boots | wc -l
36
[root at rawhide ~]# journalctl -F _BOOT_ID | wc -l
81
# cat /proc/sys/kernel/random/boot_id
1e0d5346-85cb-477b-9ae2-2cfb53097b97


So there are more boot ID's than there are list-boots, and list-boots doesn't increment while boot ID's do. And neither of these boot id's match any of the boot id's in --list-boots.


> You can also add ` -o verbose` to see all the fields of records. Since you say that the messages are actually stored in the journal, it might be interesting to check their _BOOT_ID fields.

--since=2014-05-08
_BOOT_ID=e39d1329d216487f951334b229449d81

--since=2014-05-09
_BOOT_ID=550ece50b3ed4e21b9a0c446b95c2ebd

--since=2014-05-04
_BOOT_ID=e428016363534ea595b1d9ba0440deeb


They all appear to have unique boot IDs in the journal. Yet they aren't listed in --list-boots. For whatever reason, --list-boots is a subset of what I actually have.


Chris Murphy