Linux Btrfs filesystem development
 help / color / mirror / Atom feed
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:37:31 +1030	[thread overview]
Message-ID: <a2e56b07-b0fc-485c-8a68-2136e595ec3b@suse.com> (raw)
In-Reply-To: <CAF1bhLWnf2CLnZ=BbBVS1je8a7LYacbKDAaLYNgFzY+Z1=L2=Q@mail.gmail.com>



在 2026/4/1 08:31, Jaron Viëtor 写道:
> On Tue, Mar 31, 2026 at 11:58 PM Qu Wenruo <wqu@suse.com> wrote:
[...]
>> My bad, I forgot to ask for dump-tree of dev tree:
>>
>> # btrfs ins dump-tree -t dev <device>
>>
>> Again it's fine to dump it from any good device.
> 
> No worries! Here it is: https://transfer.ddvtech.com/pY3LV9yw1L/dump_tree.txt

And the last one, from chunk tree:

# btrfs ins dump-tree -t chunk <device>

So far the result looks fine, nothing wrong so far.
All device items looks correct, with unique uuid and correct devid.
The dev-replace item in dev tree also looks sane.

The only next item to check is the device items in chunk tree.

Thanks,
Qu

  reply	other threads:[~2026-03-31 22:07 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
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 [this message]
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=a2e56b07-b0fc-485c-8a68-2136e595ec3b@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