From: Adam Borowski <kilobyte@angband.pl>
To: Chris Murphy <lists@colorremedies.com>
Cc: Simeon Felis <simeon_btrfs@sfelis.de>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Qu Wenruo <quwenruo.btrfs@gmx.com>
Subject: Re: kernel incompatibility?
Date: Tue, 18 Feb 2020 03:14:41 +0100 [thread overview]
Message-ID: <20200218021441.GA24450@angband.pl> (raw)
In-Reply-To: <CAJCQCtSUxC8uF5fAFSOGUDHfRJCY_x8uCSGZ_r_63961Tb17+g@mail.gmail.com>
On Mon, Feb 17, 2020 at 03:55:02PM -0700, Chris Murphy wrote:
> 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.
> > [ 27.304203] BTRFS critical (device sda1): unable to find logical 4306137776128 length 4096
> 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.
In particular, you have a filesystem 8TB in size on a 32-bit machine.
That's just below the limit of brokenness. If the balance allocated
enough new logical addresses...
On the other hand, the addresses mentioned here are just below 4TB.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Remember, the S in "IoT" stands for Security, while P stands
⢿⡄⠘⠷⠚⠋⠀ for Privacy.
⠈⠳⣄⠀⠀⠀⠀
next prev parent reply other threads:[~2020-02-18 2:50 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
2020-02-18 2:14 ` Adam Borowski [this message]
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=20200218021441.GA24450@angband.pl \
--to=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--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).