From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: hmsjwzb <hmsjwzb@zoho.com>
Cc: linux-btrfs@vger.kernel.org, anand.jain@oracle.com
Subject: Re: [PATCH v2] btrfs-progs: chunk tree search solution for btrfs249
Date: Tue, 16 Aug 2022 13:18:20 +0800 [thread overview]
Message-ID: <158cf69b-4797-9019-f137-7a437da5dd77@gmx.com> (raw)
In-Reply-To: <30296ee6-594c-3964-ca71-4c2fdafa4e05@zoho.com>
On 2022/8/16 10:40, hmsjwzb wrote:
> Hi Qu,
>
> IMO, for btrfs249
>
> mkfs.btrfs -d raid1 -m raid1 /dev/sdb /dev/sdc
>
> btrfstune -S 1 /dev/sdb
>
> wipefs -a /dev/sdb
>
> mount -o degraded /dev/sdc /mnt/scratch
>
> btrfs device add -f /dev/sdd /mnt/scratch
>
> After the above command, the sdb(missing deive) and sdc went to seed_list.
> So the missing device will not show by btrfs filesystem usage command.
>
> Fsid of sdb & sdc also changed in above command. Before this command,
> btrfs filesystem usage can dump out the device information of sdb & sdc.
> After that, only sdd will dump out.
>
> I think this behavior is proper.
My bad, I forgot it's fi usage, which only makes sense for RW devices.
So please discard my comment on that part.
Thanks,
Qu
>
> Thanks,
> Flint
>
> On 8/15/22 04:06, Qu Wenruo wrote:
>> This will only load the device info for rw devices.
>>
>> But no seed device will be populated, wouldn't this cause problem
>> showing missing seed devices?
next prev parent reply other threads:[~2022-08-16 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 2:43 [PATCH v2] btrfs-progs: chunk tree search solution for btrfs249 Flint.Wang
2022-08-15 8:06 ` Qu Wenruo
2022-08-16 2:40 ` hmsjwzb
2022-08-16 5:18 ` Qu Wenruo [this message]
2022-12-09 6:24 ` Qu Wenruo
2022-12-09 9:14 ` hmsjwzb
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=158cf69b-4797-9019-f137-7a437da5dd77@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=anand.jain@oracle.com \
--cc=hmsjwzb@zoho.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