> > It looks like --list-boots is broken. I have have the same problem on Rawhide > with systemd-212-4.fc21.x86_64, which is a completely different VM. Here are > the last three items with --list-boots > > -2 95117f702e4d43619072f87b20b2f31b Sat 2014-05-03 20:38:22 MDT—Sat > 2014-05-03 20:47:17 MDT > -1 c9bf102876774c7a8748920f6135ddf6 Sat 2014-05-03 20:47:35 MDT—Sat > 2014-05-03 20:51:55 MDT > 0 f92e4dda29a54b89a3455a10bbb298b2 Sat 2014-05-03 21:01:17 MDT—Sat > 2014-05-03 21:05:24 MDT
OK installed Rawhide clean today to a third VM, with a Btrfs subvolume "var" mounted at /var, and the problem doesn't occur. Each boot gets a new entry with --list-boots. The prior Rawhide and Fedora 20 meanwhile, still always have the same --list-boot list after each boot, stuck on May 3rd for some reason. So it seems something broke --list-boot in a state persistent manner with the journal files themselves. The data is in the journal file however, I can extract the prior boots with --since and --lines, it's just that -b [x] is useless. -b -1 takes me back over a week rather than the boot 30 minutes ago. Chris Murphy _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
