From: Mike Javorski <mike.javorski@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Ran into "invalid block group size" bug, unclear how to proceed.
Date: Mon, 3 Dec 2018 20:00:49 -0800 [thread overview]
Message-ID: <CAOv1SKCkw4yKTw6McoE6pOU9V7v10RRr5naMdopoVHM-COShzQ@mail.gmail.com> (raw)
In-Reply-To: <CAOv1SKD46XeF=iqi4At-0YJpK6nHQ+3ErKDN_sW_4fAPMyAgMw@mail.gmail.com>
Apologies for not scouring the mailing list completely (just
subscribed in fact) as It appears that Patrick Dijkgraaf also ran into
this issue. He went ahead with a volume rebuild, whereas I am hoping I
can recover having not run anything more than a "btrfs scan" and
"btrfs device ready" on this machine to this point since the kernel
upgrade and the FS was intact up to that point.
- mike
On Mon, Dec 3, 2018 at 7:32 PM Mike Javorski <mike.javorski@gmail.com> wrote:
>
> Need a bit of advice here ladies / gents. I am running into an issue
> which Qu Wenruo seems to have posted a patch for several weeks ago
> (see https://patchwork.kernel.org/patch/10694997/).
>
> Here is the relevant dmesg output which led me to Qu's patch.
> ----
> [ 10.032475] BTRFS critical (device sdb): corrupt leaf: root=2
> block=24655027060736 slot=20 bg_start=13188988928 bg_len=10804527104,
> invalid block group size, have 10804527104 expect (0, 10737418240]
> [ 10.032493] BTRFS error (device sdb): failed to read block groups: -5
> [ 10.053365] BTRFS error (device sdb): open_ctree failed
> ----
>
> This server has a 16 disk btrfs filesystem (RAID6) which I boot
> periodically to btrfs-send snapshots to. This machine is running
> ArchLinux and I had just updated to their latest 4.19.4 kernel
> package (from 4.18.10 which was working fine). I've tried updating to
> the 4.19.6 kernel that is in testing, but that doesn't seem to resolve
> the issue. From what I can see on kernel.org, the patch above is not
> pushed to stable or to Linus' tree.
>
> At this point the question is what to do. Is my FS toast? Could I
> revert to the 4.18.10 kernel and boot safely? I don't know if the 4.19
> boot process may have flipped some bits which would make reverting
> problematic.
>
> Thanks much,
>
> - mike
next prev parent reply other threads:[~2018-12-04 4:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 3:32 Ran into "invalid block group size" bug, unclear how to proceed Mike Javorski
2018-12-04 4:00 ` Mike Javorski [this message]
2018-12-04 5:56 ` Chris Murphy
2018-12-04 6:46 ` Mike Javorski
2018-12-04 10:18 ` Qu Wenruo
2018-12-04 22:33 ` Mike Javorski
2018-12-05 5:24 ` Qu Wenruo
2018-12-05 5:47 ` Mike Javorski
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=CAOv1SKCkw4yKTw6McoE6pOU9V7v10RRr5naMdopoVHM-COShzQ@mail.gmail.com \
--to=mike.javorski@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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).