On Linux 6.15.3+ there have been increased reports of log tree corruption being hit by users of the Btrfs file-system. Fortunately, a fix has now been submitted for Linux 6.17 Git and then for back-porting to the recent stable kernel versions.

Peter Jung of CachyOS raised one month ago [1]increased reports of corruption for the log tree with Btrfs. There have also been [2]other reports too of Btrfs log tree corruption on Linux 6.15.3+ kernels. Fortunately, in the cases I've seen reported, the corruption has been able to be fixed.

The important news now is that Btrfs maintainer David Sterba sent out [3]a pull request with a fix:

"please pull a single btrfs commit. It fixes a problem that people started to hit since 6.15.3 during log replay (e.g. after a crash). The bug is old but got more likely to happen since 5e85262e542d6da got backported to stable (6.15 only). The summer vacation time caused delays of the fix delivery, apologies to everyone. Thanks."

[4]The patch provides more insight into the log tree replay failure due to a file with zero links and extents.



[1] https://lore.kernel.org/linux-btrfs/fce139db-4458-4788-bb97-c29acf6cb1df@cachyos.org/

[2] https://lore.kernel.org/linux-btrfs/lh4W-Lwc0Mbk-QvBhhQyZxf6VbM3E8VtIvU3fPIQgweP_Q1n7wtlUZQc33sYlCKYd-o6rryJQfhHaNAOWWRKxpAXhM8NZPojzsJPyHMf2qY=@protonmail.com/#t

[3] https://lore.kernel.org/lkml/cover.1754478249.git.dsterba@suse.com/T/#u

[4] https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git/commit/?h=for-6.17-fix&id=0a32e4f0025a74c70dcab4478e9b29c22f5ecf2f