Re: Massive filesystem corruption since kernel 5.2 (ARCH)

[Qu Wenruo <quwenruo.btrfs@gmx.com>]

On 2019/7/29 下午10:34, Swâmi Petaramesh wrote:
> Le 29/07/2019 à 16:27, Qu Wenruo a écrit :
>> BTW, I'm more interesting in your other corrupted leaf report other than
>> this transid error.
>
> Well I already broke 2 FSes including my most important computer with
> this, took me 2 working days to restore and mostly fix my main computer
> which I couldn't use for a week (because of lack of time for restoring
> it) and now I lose my main backup disk.

At least from what I see in this transid error, unless you ruled out the
possibility of bad disk firmware and LVM/LUKS, it's hard to say it's
btrfs causing the problem.

In fact, we have a more experienced sysadmin, Zygo, sharing his
experience of bad *HARDWARE* causing various Flush/FUA problem, which is
not easy to hit in normal use case, but only after power loss.

So for your transid error, it's really hard to pin down the cause,
unless you have deployed hundreds btrfs...

>
> I'd really like to see this addressed, because I'm crying tears of blood...
>
>> The later one is either some real corruption from older fs, or some
>> false alerts needs to be addressed.
>
> So how could I help with this one ?

As already said in that thread, full dmesg of that mount failure.

Thanks,
Qu

>
> TIA
>
> ॐ
>