** Description changed:
+ [ Impact ]
+
+ * Journals are sometimes corrupted when rotating on BTRFS.
+ * Systemd itself handles this gracefully, but some other log parsers fail.
+
+ [ Test Plan ]
+
+ * Install Ubuntu 24.04 in a VM using BTRFS on the root filesystem.
+ * Cause a log rotation: `journalctl --rotate --vacuum-time=1s`
+ * Verify the journal: `journalctl --verify`
+
+ [ Where problems could occur ]
+
+ * It's possible that the change might cause regressions in other areas on
BTRFS, since it affects file copies in general, rather than just those in
journalctl. It should only affect copy operations that use btrfs reflinks,
though, so other filesystems aren't likely to experience regressions.
+ * This change doesn't pass autopkgtest on my machine, but the current
`ubuntu/noble-devel` branch fails the same tests. It's possible that these
failures are hiding other regressions.
+
+ [ Original report follows ]
+
I am seeing in the logs
- 1c9970: Data object references invalid entry at 29eb6c0
- File corruption detected at
/var/log/journal/ec21df2344e63eaf9659b434d0127c0c/system.journal:29eb188 (of
50331648 bytes, 87%).
+ 1c9970: Data object references invalid entry at 29eb6c0
+ File corruption detected at
/var/log/journal/ec21df2344e63eaf9659b434d0127c0c/system.journal:29eb188 (of
50331648 bytes, 87%).
This causes different log parsers to freeze. Fix already exists and have
been merged https://github.com/systemd/systemd/pull/31311
Just backporting is required to systemd 245
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.20
ProcVersionSignature: Ubuntu 5.15.0-1058.64~20.04.1-aws 5.15.148
Uname: Linux 5.15.0-1058-aws x86_64
ApportVersion: 2.20.11-0ubuntu27.26
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 14 10:58:06 2024
Ec2AMI: ami-0917237b4e71c5759
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: eu-west-2a
Ec2InstanceType: r5.2xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
-
+
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: Amazon EC2 r5.2xlarge
ProcEnviron:
- LANGUAGE=en_US.UTF-8
- TERM=xterm-256color
- PATH=(custom, no user)
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ LANGUAGE=en_US.UTF-8
+ TERM=xterm-256color
+ PATH=(custom, no user)
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1058-aws
root=PARTUUID=093eb684-01 ro console=tty1 console=ttyS0
nvme_core.io_timeout=4294967295 panic=-1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2017
dmi.bios.release: 1.0
dmi.bios.vendor: Amazon EC2
dmi.bios.version: 1.0
dmi.board.asset.tag: i-0d9253990d170b721
dmi.board.vendor: Amazon EC2
dmi.chassis.asset.tag: Amazon EC2
dmi.chassis.type: 1
dmi.chassis.vendor: Amazon EC2
dmi.modalias:
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:br1.0:svnAmazonEC2:pnr5.2xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:sku:
dmi.product.name: r5.2xlarge
dmi.sys.vendor: Amazon EC2
modified.conffile..etc.systemd.journald.conf: [modified]
mtime.conffile..etc.systemd.journald.conf: 2021-05-05T14:29:31.585136
--
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
