From: Anand Jain <p10sonu@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Goffredo Baroncelli <kreijack@libero.it>,
linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>
Subject: Re: [BUG][PATCH] btrfs: a mixed profile DUP and RAID1C3/RAID1C4 prevent to alloc a new chunk
Date: Mon, 1 Jun 2020 14:04:54 +0800 [thread overview]
Message-ID: <c767c663-d6b0-da5a-f065-fc1198fc319e@oracle.com> (raw)
In-Reply-To: <fc8f88a4-3812-a0dc-99ab-929b27d7530a@gmx.com>
>
> This in facts exposed the long existing bug that btrfs has no on-disk
> indicator for the target chunk time, thus we need to be "creative" to
> handle chunk profiles.
>
> I'm wondering if we could add new persistent item in chunk tree or super
> block to solve the problem.
>
+1. That will also fix the chunk size discrepancy between mkfs and kernel.
Thanks, Anand
> Any idea on this, David?
>
> Thanks,
> Qu
>
>>
>> [*] https://lore.kernel.org/linux-btrfs/517dac49-5f57-2754-2134-92d716e50064@alice.it/
>>
prev parent reply other threads:[~2020-06-01 6:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 18:53 [BUG][PATCH] btrfs: a mixed profile DUP and RAID1C3/RAID1C4 prevent to alloc a new chunk Goffredo Baroncelli
2020-05-30 18:53 ` [PATCH] btrfs: btrfs_reduce_alloc_profile(): add support for raid1c3/raid1c4 Goffredo Baroncelli
2020-05-31 0:51 ` [BUG][PATCH] btrfs: a mixed profile DUP and RAID1C3/RAID1C4 prevent to alloc a new chunk Qu Wenruo
2020-05-31 5:58 ` Goffredo Baroncelli
2020-06-01 6:04 ` Anand Jain [this message]
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=c767c663-d6b0-da5a-f065-fc1198fc319e@oracle.com \
--to=p10sonu@gmail.com \
--cc=dsterba@suse.cz \
--cc=kreijack@libero.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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;
as well as URLs for NNTP newsgroup(s).