From: Chris Murphy <lists@colorremedies.com>
To: Simeon Felis <simeon_btrfs@sfelis.de>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Qu Wenruo <quwenruo.btrfs@gmx.com>
Subject: Re: kernel incompatibility?
Date: Mon, 17 Feb 2020 15:55:02 -0700 [thread overview]
Message-ID: <CAJCQCtSUxC8uF5fAFSOGUDHfRJCY_x8uCSGZ_r_63961Tb17+g@mail.gmail.com> (raw)
In-Reply-To: <8fb8442b-dbf9-4d4b-42bb-ce460048f891@sfelis.de>
On Sun, Feb 16, 2020 at 2:25 AM Simeon Felis <simeon_btrfs@sfelis.de> 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
next prev parent reply other threads:[~2020-02-17 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 9:02 kernel incompatibility? Simeon Felis
2020-02-17 22:55 ` Chris Murphy [this message]
2020-02-18 2:14 ` Adam Borowski
2020-02-18 11:54 ` Henk Slager
2020-02-18 14:15 ` Chris Murphy
2020-02-18 17:20 ` Henk Slager
2020-02-18 17:22 ` Henk Slager
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJCQCtSUxC8uF5fAFSOGUDHfRJCY_x8uCSGZ_r_63961Tb17+g@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=simeon_btrfs@sfelis.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).