On Thu, Apr 15, 2021 at 2:04 AM Niccolò Belli <darkba...@linuxsystems.it> wrote: > > Full dmesg: https://pastebin.com/pNBhAPS5
This is at initial ro mount time during boot: [ 4.035226] BTRFS info (device nvme0n1p8): bdev /dev/nvme0n1p8 errs: wr 0, rd 0, flush 0, corrupt 41, gen 0 There are previously detected corruption events. This is just a simple counter. It could be the same corruption encountered 41 times, or it could be 41 separate corrupt blocks. In other words, older logs might have a clue about what first started going wrong. > I have another laptop with Arch Linux and btrfs, should I be worried > about it? Maybe it's a Fedora thing? Both are using upstream stable Btrfs code. I think the focus at this point is on tracking down a hardware cause for the two problems, however unusually bad luck that is; but also there could be a bug (e.g. repair shouldn't crash). The correct reaction to corruption on Btrfs is to update backups while you still can, while it's still mounted or can be mounted. Then try repair once the underlying problem has been rectified. -- Chris Murphy
