RE: Problems with BTRFS formatted disk

["David C. Partridge" <david.partridge@perdrix.co.uk>]

LUbuntu 22.04 was definitely 5.15 kernel, what alternative distro do you propose I use? 

-----Original Message-----
From: Qu Wenruo <quwenruo.btrfs@gmx.com> 
Sent: 19 June 2022 11:41
To: David C. Partridge <david.partridge@perdrix.co.uk>; linux-btrfs@vger.kernel.org
Subject: Re: Problems with BTRFS formatted disk



On 2022/6/19 18:29, David C. Partridge wrote:
> Booted from live USB 22.04 LUbuntu.

Ubuntu kernel version doesn't seem to be that consistent even for its
LTS releases:

https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle

Please use something rolling released distro/branch instead.

Thanks,
Qu
>
> root@lubuntu:/home/lubuntu# mount -t btrfs -o rescue=all /dev/sdc1 /mnt
> mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.
> root@lubuntu:/home/lubuntu#
>
> Content of system journal
>
> Jun 19 10:08:03 lubuntu kernel: BTRFS info (device sdc1): flagging fs with big metadata feature
> Jun 19 10:08:03 lubuntu kernel: BTRFS info (device sdc1): disk space caching is enabled
> Jun 19 10:08:03 lubuntu kernel: BTRFS info (device sdc1): has skinny extents
> Jun 19 10:08:03 lubuntu kernel: BTRFS error (device sdc1): parent transid verify failed on 12554992156672 wanted 130582 found 127355
> Jun 19 10:08:03 lubuntu kernel: BTRFS error (device sdc1): parent transid verify failed on 12554992156672 wanted 130582 found 127355
> Jun 19 10:08:03 lubuntu kernel: BTRFS error (device sdc1): failed to read block groups: -5
> Jun 19 10:08:03 lubuntu kernel: BTRFS error (device sdc1): open_ctree failed
>
> David
>
> -----Original Message-----
> From: Qu Wenruo <quwenruo.btrfs@gmx.com>
> Sent: 19 June 2022 03:02
> To: David C. Partridge <david.partridge@perdrix.co.uk>; linux-btrfs@vger.kernel.org
> Subject: Re: Problems with BTRFS formatted disk
>
>>> You can try rescue=all mount option, which has the extra handling on
>>> corrupted extent tree.
>>
>>> Although you have to use kernels newer than v5.15 (including v5.15) to
>>> benefit from the change.
>>
>> Unfortunately:
>> amonra@charon:~$ uname -a
>> Linux charon 5.4.0-113-generic #127-Ubuntu SMP Wed May 18 14:30:56 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
>
> Any special reason that you can not even use a liveUSB to boot a newer
> kernel to do the salvage?
>
>
> Thanks,
> Qu
>