Hello Willow, thank you for taking an interest in this bug. I completely understand the delay.
I can confirm that the issue still exists on current Noble version. > root@dut-vm:~# apt list --installed | grep systemd > > WARNING: apt does not have a stable CLI interface. Use with caution in > scripts. > > libnss-systemd/now 255.4-1ubuntu8.17 amd64 [installed,local] > libpam-systemd/now 255.4-1ubuntu8.17 amd64 [installed,local] > libsystemd-shared/now 255.4-1ubuntu8.17 amd64 [installed,local] > libsystemd0/now 255.4-1ubuntu8.17 amd64 [installed,local] > systemd-coredump/now 255.4-1ubuntu8.17 amd64 [installed,local] > systemd-dev/now 255.4-1ubuntu8.17 all [installed,local] > systemd-hwe-hwdb/now 255.1.7 all [installed,local] > systemd-resolved/now 255.4-1ubuntu8.17 amd64 [installed,local] > systemd-sysv/now 255.4-1ubuntu8.17 amd64 [installed,local] > systemd/now 255.4-1ubuntu8.17 amd64 [installed,local] > root@dut-vm:~# journalctl --rotate --vacuum-time=1s > Vacuuming done, freed 0B of archived journals from /run/log/journal. > Vacuuming done, freed 0B of archived journals from /var/log/journal. > Deleted archived journal > /var/log/journal/de55a3fc536044d8a5638dda179211ef/system@a847c436103f4e5c8b2ecaf8249edbb9-000000000000024e-00065b781af48bcd.journal > (4.8M). > Deleted archived journal > /var/log/journal/de55a3fc536044d8a5638dda179211ef/user-1001@a847c436103f4e5c8b2ecaf8249edbb9-0000000000000734-00065b781dade346.journal > (3.6M). > Deleted archived journal > /var/log/journal/de55a3fc536044d8a5638dda179211ef/user-1000@a847c436103f4e5c8b2ecaf8249edbb9-00000000000008d5-00065b781f1ed25c.journal > (8.0M). > Vacuuming done, freed 16.4M of archived journals from > /var/log/journal/de55a3fc536044d8a5638dda179211ef. > root@dut-vm:~# journalctl > Journal file > /var/log/journal/de55a3fc536044d8a5638dda179211ef/user-1000@a847c436103f4e5c8b2ecaf8249edbb9-00000000000008d5-00065b781f1ed25c.journal > corrupted, ignoring file. > Sep 14 23:29:42 dut-vm systemd-journald[260]: System Journal > (/var/log/journal/de55a3fc536044d8a5638dda179211ef) is 24.0M, max 1.9G, 1.9G > free. > Sep 14 23:29:43 dut-vm systemd-journald[260]: Received client request to > rotate journal, rotating. > Sep 14 23:29:43 dut-vm systemd-journald[260]: Vacuuming done, freed 0B of > archived journals from /var/log/journal/de55a3fc536044d8a5638dda179211ef. From what I understand from the original systemd issue, you need a btrfs filesystem (I'm guessing for /var/log/journal) to reproduce which is probably not the default in your container. > docker run -it ubuntu:noble df -Th > **Filesystem Type Size Used Avail Use% Mounted on > overlay overlay 915G 795G 74G 92% / [...] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2088163 Title: Journald file corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2088163/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
