Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Naohiro Aota <Naohiro.Aota@wdc.com>
Cc: David Sterba <dsterba@suse.cz>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 0/7] btrfs-progs: zoned: proper "mkfs.btrfs -b" support
Date: Tue, 14 May 2024 19:21:42 +0200	[thread overview]
Message-ID: <20240514172142.GL4449@twin.jikos.cz> (raw)
In-Reply-To: <xbrkuvkwzzwufyiqgxve67zwhwf2pxqkiiqsorbnfb3jgdug35@cs32x5a5jkv2>

On Tue, May 14, 2024 at 05:14:39PM +0000, Naohiro Aota wrote:
> On Tue, May 14, 2024 at 05:39:38PM +0200, David Sterba wrote:
> > On Mon, May 13, 2024 at 06:51:26PM -0600, Naohiro Aota wrote:
> > > mkfs.btrfs -b <byte_count> on a zoned device has several issues listed
> > > below.
> > > 
> > > - The FS size needs to be larger than minimal size that can host a btrfs,
> > >   but its calculation does not consider non-SINGLE profile
> > > - The calculation also does not ensure tree-log BG and data relocation BG
> > > - It allows creating a FS not aligned to the zone boundary
> > > - It resets all device zones beyond the specified length
> > > 
> > > This series fixes the issues with some cleanups.
> > > 
> > > Patches 1 to 3 are clean up patches, so they should not change the behavior.
> > > 
> > > Patches 4 to 6 address the issues and the last patch adds a test case.
> > > 
> > > Naohiro Aota (7):
> > >   btrfs-progs: rename block_count to byte_count
> > >   btrfs-progs: mkfs: remove duplicated device size check
> > >   btrfs-progs: mkfs: unify zoned mode minimum size calc into
> > >     btrfs_min_dev_size()
> > >   btrfs-progs: mkfs: fix minimum size calculation for zoned
> > >   btrfs-progs: mkfs: check if byte_count is zone size aligned
> > >   btrfs-progs: support byte length for zone resetting
> > >   btrfs-progs: add test for zone resetting
> > 
> > I did a quick CI check, the mkfs tests fails. You can open a pull
> > request to get your changes tested (it can be just for the testing
> > purpose, if you note that I'll skip it until the final version).
> > 
> > https://github.com/kdave/btrfs-progs/actions/runs/9081685951
> 
> Thank you. I just noticed some workflows are running on my btrfs-progs
> repository too.

Yes, the jobs are matched by the branch names and will start if you have
Actions enabled in the repository.

      reply	other threads:[~2024-05-14 17:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14  0:51 [PATCH 0/7] btrfs-progs: zoned: proper "mkfs.btrfs -b" support Naohiro Aota
2024-05-14  0:51 ` [PATCH 1/7] btrfs-progs: rename block_count to byte_count Naohiro Aota
2024-05-14  0:51 ` [PATCH 2/7] btrfs-progs: mkfs: remove duplicated device size check Naohiro Aota
2024-05-14  0:51 ` [PATCH 3/7] btrfs-progs: mkfs: unify zoned mode minimum size calc into btrfs_min_dev_size() Naohiro Aota
2024-05-14  0:51 ` [PATCH 4/7] btrfs-progs: mkfs: fix minimum size calculation for zoned Naohiro Aota
2024-05-14  0:51 ` [PATCH 5/7] btrfs-progs: mkfs: check if byte_count is zone size aligned Naohiro Aota
2024-05-14  0:51 ` [PATCH 6/7] btrfs-progs: support byte length for zone resetting Naohiro Aota
2024-05-14  0:51 ` [PATCH 7/7] btrfs-progs: add test " Naohiro Aota
2024-05-14 15:39 ` [PATCH 0/7] btrfs-progs: zoned: proper "mkfs.btrfs -b" support David Sterba
2024-05-14 17:14   ` Naohiro Aota
2024-05-14 17:21     ` David Sterba [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=20240514172142.GL4449@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=Naohiro.Aota@wdc.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