Re: kernel incompatibility?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Feb 16, 2020 at 2:25 AM Simeon Felis <simeon_btrfs@xxxxxxxxx> wrote:
>
> I had a btrfs raid1 running on raspbian (linux 4.19 arm) which overheated. To fix corruptions I attached the raid1 on my workstation (linux 5.5 x86_64) and performed scrub, defrag and --full-balance (not necessarily in this order) and fixed the corruptions.
>
> Back on raspbian a mount fails:
>
> root@omv:~# mount /dev/disk/by-label/URAID /mnt/URAID/
> mount: /mnt/URAID: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
>
> dmesg-4.19 attached.

Because you get this on 4.19.97 (which is the latest kernel on Arch
for ARM v7l), but it mounts OK on 5.5 on x86_64, I'm suspicious it's
an arch specific bug. I don't offhand see any applicable updates
through 4.19.103 that would fix this problem.

It might be interesting to know if kernel 4.19.97 on x86_64 has this
same problem.

[   26.841239] Btrfs loaded, crc32c=crc32c-generic
[   26.845640] BTRFS: device label URAID devid 7 transid 1254652 /dev/sda1
[   26.851548] BTRFS: device label URAID devid 8 transid 1254652 /dev/sdb1
[   27.301605] BTRFS info (device sda1): disk space caching is enabled
[   27.301620] BTRFS info (device sda1): has skinny extents
[   27.304203] BTRFS critical (device sda1): unable to find logical
4306137776128 length 4096
[   27.312686] BTRFS critical (device sda1): unable to find logical
4306137776128 length 4096
[   27.321193] BTRFS critical (device sda1): unable to find logical
4306137776128 length 4096
[   27.329714] BTRFS critical (device sda1): unable to find logical
4306137776128 length 4096
[   27.338227] BTRFS critical (device sda1): unable to find logical
4306137776128 length 4096
[   27.346637] BTRFS critical (device sda1): unable to find logical
4306137776128 length 4096
[   27.355110] BTRFS error (device sda1): failed to read chunk root
[   27.408326] BTRFS error (device sda1): open_ctree failed

I suggest running a (read-only no repair) 'btrfs check' using
btrfs-progs 5.4 on x86_64 and see if it complains about anything. And
also the output of a superblock, 'btrfs insp dump-s /dev/' for either
device.

-- 
Chris Murphy




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux