From: Qu Wenruo <wqu@suse.com>
To: "Jaron Viëtor" <jaron@vietors.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Problem mounting 4-drive RAID1 fs after replace was interrupted by kernel crash
Date: Wed, 1 Apr 2026 08:01:50 +1030 [thread overview]
Message-ID: <d470a043-72c0-4124-800c-385c19007b9e@suse.com> (raw)
In-Reply-To: <CAF1bhLWJuHjf8e-4o9y-hhFqadpQ=13P-PZSJLem5Q_A2T-CTw@mail.gmail.com>
在 2026/4/1 07:53, Jaron Viëtor 写道:
> On Tue, Mar 31, 2026 at 11:14 PM Qu Wenruo <wqu@suse.com> wrote:
[...]
>>
>> Kernel version please.
>>
>> And with all devices (including the new and failing disks), and "btrfs
>> dev scan", the mount still fails with the same message?
>>
>> If so, mount with "degraded" mount option, and try to cancel the
>> replacement, then try again.
>
> Thanks for your reply!
> This is on kernel 6.19.10, the problem (and start of the replace
> operation) was originally started on kernel 6.18.2 - I updated in
> hopes that would fix things, but it made no difference.
> Yes, with all drives the mount fails with the same message. Attempting
> to mount degraded (or ro,degraded) also gives the exact same message
> as well, so I have no way to cancel the replacement (that I know of).
Then please provide the following dump, just use any device is fine
(maybe except the replace target/source device):
# btrfs ins dump-tree -t root <device>
Then the following dump for each device, including the target and source
device:
# btrfs ins dump-super -f <device>
I still remember I handled a similar bug before, which seems to be a
bitflip in the devid.
And just in case, please also run a memtest to rule out any hardware
memory problems.
You won't believe how frequent such problems are observed, especially if
your NUC is running DDR4 memory.
Thanks,
Qu
>
> Kind regards,
> Jaron
>
>>
>> Thanks,
>> Q
next prev parent reply other threads:[~2026-03-31 21:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 20:39 Problem mounting 4-drive RAID1 fs after replace was interrupted by kernel crash Jaron Viëtor
2026-03-31 21:13 ` Qu Wenruo
2026-03-31 21:23 ` Jaron Viëtor
2026-03-31 21:31 ` Qu Wenruo [this message]
2026-03-31 21:54 ` Jaron Viëtor
2026-03-31 21:58 ` Qu Wenruo
2026-03-31 22:01 ` Jaron Viëtor
2026-03-31 22:07 ` Qu Wenruo
2026-03-31 22:11 ` Jaron Viëtor
2026-03-31 22:33 ` Qu Wenruo
2026-03-31 22:47 ` Jaron Viëtor
2026-04-07 5:41 ` Qu Wenruo
2026-04-07 11:31 ` Jaron Viëtor
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=d470a043-72c0-4124-800c-385c19007b9e@suse.com \
--to=wqu@suse.com \
--cc=jaron@vietors.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