The VM is reporting the errors. A power failure or crash is likely to blame. Scrubs happen monthly (3 weeks ago). No other BTRFS messages in dmesg to report, just a bunch of sudo audit's. $ sudo btrfs scrub status /mnt/raid UUID: 8c1dea88-fa40-4e6e-a1a1-214ea6bcdb00 Scrub started: Thu Feb 27 00:16:58 2020 Status: aborted Duration: 0:02:03 Total to scrub: 5.76TiB Rate: 853.91MiB/s Error summary: csum=278 Corrected: 0 Uncorrectable: 278 Unverified: 0 On Wed, Feb 26, 2020 at 11:30 PM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > > On Wed, Feb 26, 2020 at 11:00 PM 4e868df3 <4e868df3@xxxxxxxxx> wrote: > > > > I updated kernels recently and now am getting a corrupt leaf error. > > The drives decrypt and mount, and I can touch a file briefly until the > > mount switches over to read-only mode. Extended SMART tests show all 6 > > of my drives have a healthy status. I have a backup of the data. The > > array is configured as RAID10. As the BTRFS filesystem remains > > accessible / read-only, I am able to take an additional backup. What > > is the best way to recover from this error? > > > >$ uname -a > >VM: Linux server0 5.5.6-arch1-1 #1 SMP PREEMPT Mon, 24 Feb 2020 12:20:16 +0000 x86_64 GNU/Linux > >proxmox: Linux pxe 4.15.18-26-pve #1 SMP PVE 4.15.18-54 (Sat, 15 Feb 2020 15:34:24 +0100) x86_64 GNU/Linux > > Which kernel is reporting the errors? > > > [ 19.448971] BTRFS info (device dm-0): bdev /dev/mapper/luks0 errs: wr 13790, rd 387, flush 0, corrupt 3532, gen 578 > > [ 19.448977] BTRFS info (device dm-0): bdev /dev/mapper/luks5 errs: wr 13673, rd 207, flush 0, corrupt 3540, gen 705 > > Btrfs reports at mount time significant number of dropped writes, and > other issues for 2 of 6 drives. This are problems that have already > happened, the statistics are recorded in file system metadata. What's > the history that might explain this? Any power failures or crashes? > When was the last time it was scrubbed? > > >[ 130.415056] BTRFS error (device dm-0): block=2533706842112 read time tree block corruption detected > > What happens after this line? File ends here. > > What do you get for > btrfs check /dev/ > > This is readonly, and repair isn't recommended unless a dev advises > it. The check only needs to be run on one device. > > -- > Chris Murphy
