All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Chandan Babu R <chandan.babu@oracle.com>
Cc: linux-xfs@vger.kernel.org, david@fromorbit.com
Subject: Re: [PATCH V5 18/20] xfsprogs: Add mkfs option to create filesystem with large extent counters
Date: Mon, 24 Jan 2022 16:33:55 -0800	[thread overview]
Message-ID: <20220125003355.GX13540@magnolia> (raw)
In-Reply-To: <20220121052019.224605-19-chandan.babu@oracle.com>

> xfsprogs: Add mkfs option to create filesystem with large extent
> counters

This ought to be shorter and more direct about this being an mkfs
patch:

"mkfs: add option to create filesystem with large extent counters"

On Fri, Jan 21, 2022 at 10:50:17AM +0530, Chandan Babu R wrote:
> Enabling nrext64 option on mkfs.xfs command line extends the maximum values of
> inode data and attr fork extent counters to 2^48 - 1 and 2^32 - 1
> respectively.  This also sets the XFS_SB_FEAT_INCOMPAT_NREXT64 incompat flag
> on the superblock preventing older kernels from mounting such a filesystem.
> 
> Reviewed-by: Darrick J. Wong <djwong@kernel.org>
> Signed-off-by: Chandan Babu R <chandan.babu@oracle.com>
> ---
>  man/man8/mkfs.xfs.8.in |  7 +++++++
>  mkfs/lts_4.19.conf     |  1 +
>  mkfs/lts_5.10.conf     |  1 +
>  mkfs/lts_5.15.conf     |  1 +
>  mkfs/lts_5.4.conf      |  1 +
>  mkfs/xfs_mkfs.c        | 23 +++++++++++++++++++++++
>  6 files changed, 34 insertions(+)
> 
> diff --git a/man/man8/mkfs.xfs.8.in b/man/man8/mkfs.xfs.8.in
> index a3526753..7d764f19 100644
> --- a/man/man8/mkfs.xfs.8.in
> +++ b/man/man8/mkfs.xfs.8.in
> @@ -647,6 +647,13 @@ space over time such that no free extents are large enough to
>  accommodate a chunk of 64 inodes. Without this feature enabled, inode
>  allocations can fail with out of space errors under severe fragmented
>  free space conditions.
> +.TP
> +.BI nrext64[= value]
> +Extend maximum values of inode data and attr fork extent counters from 2^31 -
> +1 and 2^15 - 1 to 2^48 - 1 and 2^32 - 1 respectively. If the value is
> +omitted, 1 is assumed. This feature is disabled by default. This feature is
> +only available for filesystems formatted with -m crc=1.
> +.TP
>  .RE
>  .PP
>  .PD 0
> diff --git a/mkfs/lts_4.19.conf b/mkfs/lts_4.19.conf
> index d21fcb7e..751be45e 100644
> --- a/mkfs/lts_4.19.conf
> +++ b/mkfs/lts_4.19.conf
> @@ -2,6 +2,7 @@
>  # kernel was released at the end of 2018.
>  
>  [metadata]
> +nrext64=0
>  bigtime=0
>  crc=1
>  finobt=1
> diff --git a/mkfs/lts_5.10.conf b/mkfs/lts_5.10.conf
> index ac00960e..a1c991ce 100644
> --- a/mkfs/lts_5.10.conf
> +++ b/mkfs/lts_5.10.conf
> @@ -2,6 +2,7 @@
>  # kernel was released at the end of 2020.
>  
>  [metadata]
> +nrext64=0
>  bigtime=0
>  crc=1
>  finobt=1
> diff --git a/mkfs/lts_5.15.conf b/mkfs/lts_5.15.conf
> index 32082958..d751f4c4 100644
> --- a/mkfs/lts_5.15.conf
> +++ b/mkfs/lts_5.15.conf
> @@ -2,6 +2,7 @@
>  # kernel was released at the end of 2021.
>  
>  [metadata]
> +nrext64=0
>  bigtime=1
>  crc=1
>  finobt=1
> diff --git a/mkfs/lts_5.4.conf b/mkfs/lts_5.4.conf
> index dd60b9f1..7e8a0ff0 100644
> --- a/mkfs/lts_5.4.conf
> +++ b/mkfs/lts_5.4.conf
> @@ -2,6 +2,7 @@
>  # kernel was released at the end of 2019.
>  
>  [metadata]
> +nrext64=0
>  bigtime=0
>  crc=1
>  finobt=1
> diff --git a/mkfs/xfs_mkfs.c b/mkfs/xfs_mkfs.c
> index 96682f9a..28aca7b0 100644
> --- a/mkfs/xfs_mkfs.c
> +++ b/mkfs/xfs_mkfs.c
> @@ -79,6 +79,7 @@ enum {
>  	I_ATTR,
>  	I_PROJID32BIT,
>  	I_SPINODES,
> +	I_NREXT64,
>  	I_MAX_OPTS,
>  };
>  
> @@ -433,6 +434,7 @@ static struct opt_params iopts = {
>  		[I_ATTR] = "attr",
>  		[I_PROJID32BIT] = "projid32bit",
>  		[I_SPINODES] = "sparse",
> +		[I_NREXT64] = "nrext64",
>  	},
>  	.subopt_params = {
>  		{ .index = I_ALIGN,
> @@ -481,6 +483,12 @@ static struct opt_params iopts = {
>  		  .maxval = 1,
>  		  .defaultval = 1,
>  		},
> +		{ .index = I_NREXT64,
> +		  .conflicts = { { NULL, LAST_CONFLICT } },
> +		  .minval = 0,
> +		  .maxval = 1,
> +		  .defaultval = 1,
> +		}
>  	},
>  };
>  
> @@ -805,6 +813,7 @@ struct sb_feat_args {
>  	bool	bigtime;		/* XFS_SB_FEAT_INCOMPAT_BIGTIME */
>  	bool	nodalign;
>  	bool	nortalign;
> +	bool	nrext64;
>  };
>  
>  struct cli_params {
> @@ -1595,6 +1604,9 @@ inode_opts_parser(
>  	case I_SPINODES:
>  		cli->sb_feat.spinodes = getnum(value, opts, subopt);
>  		break;
> +	case I_NREXT64:
> +		cli->sb_feat.nrext64 = getnum(value, opts, subopt);
> +		break;
>  	default:
>  		return -EINVAL;
>  	}
> @@ -2172,6 +2184,14 @@ _("timestamps later than 2038 not supported without CRC support\n"));
>  			usage();
>  		}
>  		cli->sb_feat.bigtime = false;
> +
> +		if (cli->sb_feat.nrext64 &&
> +			cli_opt_set(&iopts, I_NREXT64)) {
> +			fprintf(stderr,

Nit: second line of if test has the same indentation level as the first
line of the if body.

With those two things fixed,
Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D


> +_("64 bit extent count not supported without CRC support\n"));
> +			usage();
> +		}
> +		cli->sb_feat.nrext64 = false;
>  	}
>  
>  	if (!cli->sb_feat.finobt) {
> @@ -3164,6 +3184,8 @@ sb_set_features(
>  		sbp->sb_features_incompat |= XFS_SB_FEAT_INCOMPAT_SPINODES;
>  	}
>  
> +	if (fp->nrext64)
> +		sbp->sb_features_incompat |= XFS_SB_FEAT_INCOMPAT_NREXT64;
>  }
>  
>  /*
> @@ -3875,6 +3897,7 @@ main(
>  			.nodalign = false,
>  			.nortalign = false,
>  			.bigtime = true,
> +			.nrext64 = false,
>  			/*
>  			 * When we decide to enable a new feature by default,
>  			 * please remember to update the mkfs conf files.
> -- 
> 2.30.2
> 

  reply	other threads:[~2022-01-25  2:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21  5:19 [PATCH V5 00/20] xfsprogs: Extend per-inode extent counters Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 01/20] xfs_repair: check filesystem geometry before allowing upgrades Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 02/20] xfsprogs: Move extent count limits to xfs_format.h Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 03/20] xfsprogs: Introduce xfs_iext_max_nextents() helper Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 04/20] xfsprogs: Use xfs_extnum_t instead of basic data types Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 05/20] xfsprogs: Introduce xfs_dfork_nextents() helper Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 06/20] xfsprogs: Use basic types to define xfs_log_dinode's di_nextents and di_anextents Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 07/20] xfsprogs: Promote xfs_extnum_t and xfs_aextnum_t to 64 and 32-bits respectively Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 08/20] xfsprogs: Introduce XFS_SB_FEAT_INCOMPAT_NREXT64 and associated per-fs feature bit Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 09/20] xfsprogs: Introduce XFS_FSOP_GEOM_FLAGS_NREXT64 Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 10/20] xfsprogs: Introduce XFS_DIFLAG2_NREXT64 and associated helpers Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 11/20] xfsprogs: Use xfs_rfsblock_t to count maximum blocks that can be used by BMBT Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 12/20] xfsprogs: Introduce macros to represent new maximum extent counts for data/attr forks Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 13/20] xfsprogs: Introduce per-inode 64-bit extent counters Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 14/20] xfsprogs: Conditionally upgrade existing inodes to use " Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 15/20] xfsprogs: Enable bulkstat ioctl to support " Chandan Babu R
2022-02-01 19:29   ` Darrick J. Wong
2022-01-21  5:20 ` [PATCH V5 16/20] xfsprogs: Add XFS_SB_FEAT_INCOMPAT_NREXT64 to the list of supported flags Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 17/20] xfsprogs: xfs_info: Report NREXT64 feature status Chandan Babu R
2022-01-21  5:20 ` [PATCH V5 18/20] xfsprogs: Add mkfs option to create filesystem with large extent counters Chandan Babu R
2022-01-25  0:33   ` Darrick J. Wong [this message]
2022-01-21  5:20 ` [PATCH V5 19/20] xfsprogs: Add support for upgrading to NREXT64 feature Chandan Babu R
2022-01-25  0:35   ` Darrick J. Wong
2022-01-21  5:20 ` [PATCH V5 20/20] xfsprogs: Define max extent length based on on-disk format definition Chandan Babu R

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=20220125003355.GX13540@magnolia \
    --to=djwong@kernel.org \
    --cc=chandan.babu@oracle.com \
    --cc=david@fromorbit.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.