From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, Wang Yugui <wangyugui@e16-tech.com>
Subject: Re: [PATCH] btrfs: fix the max chunk size and stripe length calculation
Date: Tue, 6 Sep 2022 18:01:16 +0200 [thread overview]
Message-ID: <20220906160116.GP13489@twin.jikos.cz> (raw)
In-Reply-To: <17e7c38b0cc6fe90c90f4b383734c06eafd2f9b5.1660806386.git.wqu@suse.com>
On Thu, Aug 18, 2022 at 03:06:44PM +0800, Qu Wenruo wrote:
> [BEHAVIOR CHANGE]
> Since commit f6fca3917b4d ("btrfs: store chunk size in space-info
> struct"), btrfs no longer can create larger data chunks than 1G:
>
> mkfs.btrfs -f -m raid1 -d raid0 $dev1 $dev2 $dev3 $dev4
> mount $dev1 $mnt
>
> btrfs balance start --full $mnt
> btrfs balance start --full $mnt
> umount $mnt
>
> btrfs ins dump-tree -t chunk $dev1 | grep "DATA|RAID0" -C 2
>
> Before that offending commit, what we got is a 4G data chunk:
>
> item 6 key (FIRST_CHUNK_TREE CHUNK_ITEM 9492758528) itemoff 15491 itemsize 176
> length 4294967296 owner 2 stripe_len 65536 type DATA|RAID0
> io_align 65536 io_width 65536 sector_size 4096
> num_stripes 4 sub_stripes 1
>
> Now what we got is only 1G data chunk:
>
> item 6 key (FIRST_CHUNK_TREE CHUNK_ITEM 6271533056) itemoff 15491 itemsize 176
> length 1073741824 owner 2 stripe_len 65536 type DATA|RAID0
> io_align 65536 io_width 65536 sector_size 4096
> num_stripes 4 sub_stripes 1
>
> This will increase the number of data chunks by the number of devices,
> not only increase system chunk usage, but also greatly increase mount
> time.
>
> Without a properly reason, we should not change the max chunk size.
>
> [CAUSE]
> Previously, we set max data chunk size to 10G, while max data stripe
> length to 1G.
>
> Commit f6fca3917b4d ("btrfs: store chunk size in space-info struct")
> completely ignored the 10G limit, but use 1G max stripe limit instead,
> causing above shrink in max data chunk size.
>
> [FIX]
> Fix the max data chunk size to 10G, and in decide_stripe_size_regular()
> we limit stripe_size to 1G manually.
>
> This should only affect data chunks, as for metadata chunks we always
> set the max stripe size the same as max chunk size (256M or 1G
> depending on fs size).
>
> Now the same script result the same old result:
>
> item 6 key (FIRST_CHUNK_TREE CHUNK_ITEM 9492758528) itemoff 15491 itemsize 176
> length 4294967296 owner 2 stripe_len 65536 type DATA|RAID0
> io_align 65536 io_width 65536 sector_size 4096
> num_stripes 4 sub_stripes 1
>
> Reported-by: Wang Yugui <wangyugui@e16-tech.com>
> Fixes: f6fca3917b4d ("btrfs: store chunk size in space-info struct")
> Signed-off-by: Qu Wenruo <wqu@suse.com>
Added to misc-next, thanks. And thanks to Wang Yugui for the report.
next prev parent reply other threads:[~2022-09-06 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 7:06 [PATCH] btrfs: fix the max chunk size and stripe length calculation Qu Wenruo
2022-08-18 8:04 ` Wang Yugui
2022-08-18 8:13 ` Qu Wenruo
2022-09-06 16:01 ` David Sterba [this message]
2022-09-07 10:37 ` Wang Yugui
2022-09-07 10:44 ` Qu Wenruo
2022-09-14 21:54 ` Filipe Manana
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=20220906160116.GP13489@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangyugui@e16-tech.com \
--cc=wqu@suse.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