Skip to content

Please backport systemd/systemd#31311 to v252 (Debian 12) #382

Open
@smcv

Description

@smcv

systemd version the issue has been seen with

252.22-1~deb12u1

Used distribution

Debian 12

Linux kernel version used

6.1.0-20-amd64 (6.1.85-1)

CPU architectures issue was seen on

x86_64

Component

No response

Expected behaviour you didn't see

User journals rotated on btrfs without validation errors

Unexpected behaviour you saw

See systemd/systemd#24150, systemd/systemd#31222

Steps to reproduce the problem

  • Have /var/log on btrfs
  • Have a short-lived user session (in my case root using sudo to drop privileges to a backup user for a nightly backup job)
  • Wait for log rotation
  • The user's log gets corrupted as described on the mainline bug reports (in my case it is the backup user's journal, and root's journal remains valid)

Additional program output to the terminal or log subsystem illustrating the issue

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions