From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>, kreijack@inwind.it
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Question: how understand the raid profile of a btrfs filesystem
Date: Sat, 21 Mar 2020 08:40:50 +0300 [thread overview]
Message-ID: <bd70e1fc-5e5b-672b-cc7c-0cd9b8b31e4a@gmail.com> (raw)
In-Reply-To: <20200321032911.GR13306@hungrycats.org>
21.03.2020 06:29, Zygo Blaxell пишет:
> On Fri, Mar 20, 2020 at 06:56:38PM +0100, Goffredo Baroncelli wrote:
>> Hi all,
>>
>> for a btrfs filesystem, how an user can understand which is the {data,mmetadata,system} [raid] profile in use ? E.g. the next chunk which profile will have ?
>
> It's the profile used by the highest-numbered block group for the
> allocation type (one for data, one for metadata/system).
Is "highest-numbered" block group always the last one created? Can block
group numbers wrap around?
Recently someone reported that after conversion block groups with old
profile remained and this probably explains it - conversion races with
new allocation.
>> So the question is: the next chunk which profile will have ?
>> Is there any way to understand what will happens ?
Well, from that explanation it is not possible using standard tools -
one needs to crawl btrfs internals to find out the "last" block group.
next prev parent reply other threads:[~2020-03-21 5:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 17:56 Question: how understand the raid profile of a btrfs filesystem Goffredo Baroncelli
2020-03-21 3:29 ` Zygo Blaxell
2020-03-21 5:40 ` Andrei Borzenkov [this message]
2020-03-21 7:14 ` Zygo Blaxell
2020-03-21 9:55 ` Goffredo Baroncelli
2020-03-21 23:26 ` Zygo Blaxell
2020-03-22 8:34 ` Goffredo Baroncelli
2020-03-22 8:38 ` Goffredo Baroncelli
2020-03-22 23:49 ` Zygo Blaxell
2020-03-23 20:50 ` Goffredo Baroncelli
2020-03-23 22:48 ` Graham Cobb
2020-03-25 4:09 ` Zygo Blaxell
2020-03-25 4:30 ` Paul Jones
2020-03-26 2:51 ` Zygo Blaxell
2020-03-23 23:18 ` Zygo Blaxell
2020-03-24 4:55 ` Anand Jain
2020-03-24 17:59 ` Goffredo Baroncelli
2020-03-25 4:09 ` Andrei Borzenkov
2020-03-25 17:14 ` Goffredo Baroncelli
2020-03-26 3:10 ` Zygo Blaxell
-- strict thread matches above, loose matches on Subject: below --
2020-03-20 17:58 Goffredo Baroncelli
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=bd70e1fc-5e5b-672b-cc7c-0cd9b8b31e4a@gmail.com \
--to=arvidjaar@gmail.com \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=kreijack@inwind.it \
--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