From: Goffredo Baroncelli <kreijack@inwind.it>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Question: how understand the raid profile of a btrfs filesystem
Date: Sun, 22 Mar 2020 09:34:07 +0100 [thread overview]
Message-ID: <3fb93a14-3608-0f64-cf5c-ca37869a76ef@inwind.it> (raw)
In-Reply-To: <20200321232638.GD2693@hungrycats.org>
Hi Zygo,
On 3/22/20 12:26 AM, Zygo Blaxell wrote:
> On Sat, Mar 21, 2020 at 10:55:32AM +0100, Goffredo Baroncelli wrote:
>> On 3/21/20 4:29 AM, Zygo Blaxell wrote:
>>> On Fri, Mar 20, 2020 at 06:56:38PM +0100, Goffredo Baroncelli wrote:
>>>> Hi all,
>>>>
[...]
> ...but now you are not running conversion any more, and have multiple
> profiles. It's not really specified what will happen under those
> conditions, nor is it obvious what the correct behavior should be.
>
> The on-disk format does not have a field for "target profile".
Ok, I looked for a confirmation of that.
> Adding one would be a disk format change.
Yes but I think that it would be done in a backward compatible way. I
think to add a field "target profile" in the super-block. The old
kernels will ignore this field, and behave as today. The new ones will
allocates the new chunk according to this field.
To me it seems complicated to
Any thoughts ?
BR
G.Baroncelli
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2020-03-22 8:35 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
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 [this message]
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=3fb93a14-3608-0f64-cf5c-ca37869a76ef@inwind.it \
--to=kreijack@inwind.it \
--cc=ce3g8jdj@umail.furryterror.org \
--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