From: Christoph Hellwig <hch@infradead.org>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v2 2/2] btrfs-progs: set the proper minimum size for a zoned file system
Date: Fri, 7 Jul 2023 04:38:10 -0700 [thread overview]
Message-ID: <ZKf5IjoGAAdkrz1I@infradead.org> (raw)
In-Reply-To: <c1cfe98ea6c2610373d11d4df7c8855e6e98d3dc.1688658745.git.josef@toxicpanda.com>
On Thu, Jul 06, 2023 at 11:54:00AM -0400, Josef Bacik wrote:
> We currently limit the size of the file system to 5 * the zone size,
> however we actually want to limit it to 7 * the zone size. Fix up the
> comment and the math to match our actual minimum zoned file system size.
Hmm. IS this actually correct? Don't we also need at least a second
metadata and system block group in case the first one fills up and
metadata needs to go somewhere else to be able to reset the previous
ones?
Sorry, should have noticed that last time around.
next prev parent reply other threads:[~2023-07-07 11:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 15:53 [PATCH v2 0/2] btrfs-progs: some zoned mkfs fixups Josef Bacik
2023-07-06 15:53 ` [PATCH v2 1/2] btrfs-progs: print out the correct minimum size for zoned file systems Josef Bacik
2023-07-07 11:36 ` Christoph Hellwig
2023-07-06 15:54 ` [PATCH v2 2/2] btrfs-progs: set the proper minimum size for a zoned file system Josef Bacik
2023-07-07 11:38 ` Christoph Hellwig [this message]
2023-07-10 0:57 ` Naohiro Aota
2023-07-10 5:28 ` hch
2023-07-13 18:19 ` David Sterba
2023-07-21 6:43 ` Naohiro Aota
2023-07-10 0:59 ` Naohiro Aota
2023-07-07 9:10 ` [PATCH v2 0/2] btrfs-progs: some zoned mkfs fixups Johannes Thumshirn
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=ZKf5IjoGAAdkrz1I@infradead.org \
--to=hch@infradead.org \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.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;
as well as URLs for NNTP newsgroup(s).