On Tue, May 12, 2020 at 04:15:38PM +0200, David Sterba wrote: > generic/457 [05:40:52][17606.984360] run fstests generic/457 at 2020-05-04 05:40:52 > [17608.092098] BTRFS critical (device dm-0): corrupt leaf: root=18446744073709551610 block=30949376 slot=104, csum end range (13807616) goes beyond the start range (13717504) of the next csum item > [17608.098129] BTRFS info (device dm-0): leaf 30949376 gen 6 total ptrs 121 free space 6325 owner 18446744073709551610 > [17608.102727] BTRFS info (device dm-0): refs 2 lock (w:0 r:0 bw:0 br:0 sw:0 sr:0) lock_owner 0 current 27162 > [17608.645834] BTRFS error (device dm-0): block=30949376 write time tree block corruption detected > [17608.650272] WARNING: CPU: 2 PID: 27162 at fs/btrfs/disk-io.c:537 btree_csum_one_bio+0x297/0x2a0 [btrfs] Fixed in misc-next by Filipe's patch "btrfs: fix corrupt log due to concurrent fsync of inodes with shared extents".
