From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Carlos Maiolino <cmaiolino@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 4/4] mkfs: use a sensible log sector size default
Date: Fri, 12 Jan 2024 08:53:35 -0800 [thread overview]
Message-ID: <20240112165335.GX722975@frogsfrogsfrogs> (raw)
In-Reply-To: <20240112044743.2254211-5-hch@lst.de>
On Fri, Jan 12, 2024 at 05:47:43AM +0100, Christoph Hellwig wrote:
> Currently the XFS log sector size defaults to the 512 bytes unless
> explicitly overriden. Default to the device logical block size queried
> by get_topology instead. If that is also 512 nothing changes, and if
> the device logical block size is larged this prevents a mkfs failure
larger
> because the libxfs buffer cache blows up and as we obviously can't
> use a smaller than hardware supported sector size. This fixes xfs/157
> with a 4k block size device.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> mkfs/xfs_mkfs.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
> index be65ccc1e..022a11a7f 100644
> --- a/mkfs/xfs_mkfs.c
> +++ b/mkfs/xfs_mkfs.c
> @@ -2075,7 +2075,8 @@ static void
> validate_log_sectorsize(
> struct mkfs_params *cfg,
> struct cli_params *cli,
> - struct mkfs_default_params *dft)
> + struct mkfs_default_params *dft,
> + struct fs_topology *ft)
> {
>
> if (cli->loginternal && cli->lsectorsize &&
> @@ -2090,7 +2091,7 @@ _("Can't change sector size on internal log!\n"));
> else if (cli->loginternal)
> cfg->lsectorsize = cfg->sectorsize;
> else
> - cfg->lsectorsize = dft->sectorsize;
> + cfg->lsectorsize = ft->log.logical_sector_size;
Yessssssssss!
With the typo fixed,
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> cfg->lsectorlog = libxfs_highbit32(cfg->lsectorsize);
>
> if (cfg->lsectorsize < XFS_MIN_SECTORSIZE ||
> @@ -4196,7 +4197,7 @@ main(
> blocksize = cfg.blocksize;
> sectorsize = cfg.sectorsize;
>
> - validate_log_sectorsize(&cfg, &cli, &dft);
> + validate_log_sectorsize(&cfg, &cli, &dft, &ft);
> validate_sb_features(&cfg, &cli);
>
> /*
> --
> 2.39.2
>
>
prev parent reply other threads:[~2024-01-12 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 4:47 fix log sector size detection Christoph Hellwig
2024-01-12 4:47 ` [PATCH 1/4] libxfs: remove the unused fs_topology_t typedef Christoph Hellwig
2024-01-12 16:44 ` Darrick J. Wong
2024-01-12 16:48 ` Christoph Hellwig
2024-01-12 16:54 ` Darrick J. Wong
2024-01-12 4:47 ` [PATCH 2/4] libxfs: refactor the fs_topology structure Christoph Hellwig
2024-01-12 16:52 ` Darrick J. Wong
2024-01-12 4:47 ` [PATCH 3/4] libxfs: also query log device topology in get_topology Christoph Hellwig
2024-01-12 16:52 ` Darrick J. Wong
2024-01-12 4:47 ` [PATCH 4/4] mkfs: use a sensible log sector size default Christoph Hellwig
2024-01-12 16:53 ` Darrick J. Wong [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=20240112165335.GX722975@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cmaiolino@redhat.com \
--cc=hch@lst.de \
--cc=linux-xfs@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