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 V4 19/20] xfsprogs: Add support for upgrading to NREXT64 feature
Date: Tue, 4 Jan 2022 17:17:31 -0800 [thread overview]
Message-ID: <20220105011731.GF656707@magnolia> (raw)
In-Reply-To: <20211214084811.764481-20-chandan.babu@oracle.com>
On Tue, Dec 14, 2021 at 02:18:10PM +0530, Chandan Babu R wrote:
> This commit adds support to xfs_repair to allow upgrading an existing
> filesystem to support per-inode large extent counters.
>
> Signed-off-by: Chandan Babu R <chandan.babu@oracle.com>
> ---
> repair/globals.c | 1 +
> repair/globals.h | 1 +
> repair/phase2.c | 35 ++++++++++++++++++++++++++++++++++-
> repair/xfs_repair.c | 11 +++++++++++
> 4 files changed, 47 insertions(+), 1 deletion(-)
>
> diff --git a/repair/globals.c b/repair/globals.c
> index d89507b1..2f29391a 100644
> --- a/repair/globals.c
> +++ b/repair/globals.c
> @@ -53,6 +53,7 @@ bool add_bigtime; /* add support for timestamps up to 2486 */
> bool add_finobt; /* add free inode btrees */
> bool add_reflink; /* add reference count btrees */
> bool add_rmapbt; /* add reverse mapping btrees */
> +bool add_nrext64;
>
> /* misc status variables */
>
> diff --git a/repair/globals.h b/repair/globals.h
> index 53ff2532..af0bcb6b 100644
> --- a/repair/globals.h
> +++ b/repair/globals.h
> @@ -94,6 +94,7 @@ extern bool add_bigtime; /* add support for timestamps up to 2486 */
> extern bool add_finobt; /* add free inode btrees */
> extern bool add_reflink; /* add reference count btrees */
> extern bool add_rmapbt; /* add reverse mapping btrees */
> +extern bool add_nrext64;
>
> /* misc status variables */
>
> diff --git a/repair/phase2.c b/repair/phase2.c
> index c811ed5d..c9db3281 100644
> --- a/repair/phase2.c
> +++ b/repair/phase2.c
> @@ -191,6 +191,7 @@ check_new_v5_geometry(
> struct xfs_perag *pag;
> xfs_agnumber_t agno;
> xfs_ino_t rootino;
> + uint old_bm_maxlevels[2];
> int min_logblocks;
> int error;
>
> @@ -201,6 +202,12 @@ check_new_v5_geometry(
> memcpy(&old_sb, &mp->m_sb, sizeof(struct xfs_sb));
> memcpy(&mp->m_sb, new_sb, sizeof(struct xfs_sb));
>
> + old_bm_maxlevels[0] = mp->m_bm_maxlevels[0];
> + old_bm_maxlevels[1] = mp->m_bm_maxlevels[1];
> +
> + xfs_bmap_compute_maxlevels(mp, XFS_DATA_FORK);
> + xfs_bmap_compute_maxlevels(mp, XFS_ATTR_FORK);
Ahh... I see why you added my (evil) patch that allows upgrading a
filesystem to reflink -- you need the check_new_v5_geometry function so
that you can check if the log size is big enough to handle larger bmbt
trees.
Hmm, I guess I should work on separating this from the actual
rmap/reflink/finobt upgrade code, since I have no idea if we /ever/ want
to support that.
--D
> +
> /* Do we have a big enough log? */
> min_logblocks = libxfs_log_calc_minimum_size(mp);
> if (old_sb.sb_logblocks < min_logblocks) {
> @@ -288,6 +295,9 @@ check_new_v5_geometry(
> pag->pagi_init = 0;
> }
>
> + mp->m_bm_maxlevels[0] = old_bm_maxlevels[0];
> + mp->m_bm_maxlevels[1] = old_bm_maxlevels[1];
> +
> /*
> * Put back the old superblock.
> */
> @@ -366,6 +376,28 @@ set_rmapbt(
> return true;
> }
>
> +static bool
> +set_nrext64(
> + struct xfs_mount *mp,
> + struct xfs_sb *new_sb)
> +{
> + if (!xfs_sb_version_hascrc(&mp->m_sb)) {
> + printf(
> + _("Nrext64 only supported on V5 filesystems.\n"));
> + exit(0);
> + }
> +
> + if (xfs_sb_version_hasnrext64(&mp->m_sb)) {
> + printf(_("Filesystem already supports nrext64.\n"));
> + exit(0);
> + }
> +
> + printf(_("Adding nrext64 to filesystem.\n"));
> + new_sb->sb_features_incompat |= XFS_SB_FEAT_INCOMPAT_NREXT64;
> + new_sb->sb_features_incompat |= XFS_SB_FEAT_INCOMPAT_NEEDSREPAIR;
> + return true;
> +}
> +
> /* Perform the user's requested upgrades on filesystem. */
> static void
> upgrade_filesystem(
> @@ -388,7 +420,8 @@ upgrade_filesystem(
> dirty |= set_reflink(mp, &new_sb);
> if (add_rmapbt)
> dirty |= set_rmapbt(mp, &new_sb);
> -
> + if (add_nrext64)
> + dirty |= set_nrext64(mp, &new_sb);
> if (!dirty)
> return;
>
> diff --git a/repair/xfs_repair.c b/repair/xfs_repair.c
> index e250a5bf..96c9bb56 100644
> --- a/repair/xfs_repair.c
> +++ b/repair/xfs_repair.c
> @@ -70,6 +70,7 @@ enum c_opt_nums {
> CONVERT_FINOBT,
> CONVERT_REFLINK,
> CONVERT_RMAPBT,
> + CONVERT_NREXT64,
> C_MAX_OPTS,
> };
>
> @@ -80,6 +81,7 @@ static char *c_opts[] = {
> [CONVERT_FINOBT] = "finobt",
> [CONVERT_REFLINK] = "reflink",
> [CONVERT_RMAPBT] = "rmapbt",
> + [CONVERT_NREXT64] = "nrext64",
> [C_MAX_OPTS] = NULL,
> };
>
> @@ -357,6 +359,15 @@ process_args(int argc, char **argv)
> _("-c rmapbt only supports upgrades\n"));
> add_rmapbt = true;
> break;
> + case CONVERT_NREXT64:
> + if (!val)
> + do_abort(
> + _("-c nrext64 requires a parameter\n"));
> + if (strtol(val, NULL, 0) != 1)
> + do_abort(
> + _("-c nrext64 only supports upgrades\n"));
> + add_nrext64 = true;
> + break;
> default:
> unknown('c', val);
> break;
> --
> 2.30.2
>
next prev parent reply other threads:[~2022-01-05 1:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 8:47 [PATCH V4 00/20] xfsprogs: Extend per-inode extent counters Chandan Babu R
2021-12-14 8:47 ` [PATCH V4 01/20] xfsprogs: xfs_repair: allow administrators to add older v5 features Chandan Babu R
2021-12-14 8:47 ` [PATCH V4 02/20] xfsprogs: Move extent count limits to xfs_format.h Chandan Babu R
2021-12-14 8:47 ` [PATCH V4 03/20] xfsprogs: Introduce xfs_iext_max_nextents() helper Chandan Babu R
2021-12-14 8:47 ` [PATCH V4 04/20] xfsprogs: Use xfs_extnum_t instead of basic data types Chandan Babu R
2021-12-14 8:47 ` [PATCH V4 05/20] xfsprogs: Introduce xfs_dfork_nextents() helper Chandan Babu R
2021-12-14 8:47 ` [PATCH V4 06/20] xfsprogs: Use basic types to define xfs_log_dinode's di_nextents and di_anextents Chandan Babu R
2021-12-14 8:47 ` [PATCH V4 07/20] xfsprogs: Promote xfs_extnum_t and xfs_aextnum_t to 64 and 32-bits respectively Chandan Babu R
2021-12-14 8:47 ` [PATCH V4 08/20] xfsprogs: Introduce XFS_SB_FEAT_INCOMPAT_NREXT64 and associated per-fs feature bit Chandan Babu R
2021-12-14 8:48 ` [PATCH V4 09/20] xfsprogs: Introduce XFS_FSOP_GEOM_FLAGS_NREXT64 Chandan Babu R
2021-12-14 8:48 ` [PATCH V4 10/20] xfsprogs: Introduce XFS_DIFLAG2_NREXT64 and associated helpers Chandan Babu R
2022-01-05 1:08 ` Darrick J. Wong
2022-01-05 14:15 ` Chandan Babu R
2021-12-14 8:48 ` [PATCH V4 11/20] xfsprogs: Use xfs_rfsblock_t to count maximum blocks that can be used by BMBT Chandan Babu R
2021-12-14 8:48 ` [PATCH V4 12/20] xfsprogs: Introduce macros to represent new maximum extent counts for data/attr forks Chandan Babu R
2021-12-14 8:48 ` [PATCH V4 13/20] xfsprogs: Introduce per-inode 64-bit extent counters Chandan Babu R
2022-01-05 1:12 ` Darrick J. Wong
2022-01-07 16:10 ` Chandan Babu R
2021-12-14 8:48 ` [PATCH V4 14/20] xfsprogs: Conditionally upgrade existing inodes to use " Chandan Babu R
2021-12-14 8:48 ` [PATCH V4 15/20] xfsprogs: Enable bulkstat ioctl to support " Chandan Babu R
2022-01-05 1:13 ` Darrick J. Wong
2021-12-14 8:48 ` [PATCH V4 16/20] xfsprogs: Add XFS_SB_FEAT_INCOMPAT_NREXT64 to the list of supported flags Chandan Babu R
2021-12-14 8:48 ` [PATCH V4 17/20] xfsprogs: xfs_info: Report NREXT64 feature status Chandan Babu R
2022-01-05 1:13 ` Darrick J. Wong
2021-12-14 8:48 ` [PATCH V4 18/20] xfsprogs: Add mkfs option to create filesystem with large extent counters Chandan Babu R
2022-01-05 1:15 ` Darrick J. Wong
2021-12-14 8:48 ` [PATCH V4 19/20] xfsprogs: Add support for upgrading to NREXT64 feature Chandan Babu R
2022-01-05 1:17 ` Darrick J. Wong [this message]
2022-01-07 16:17 ` Chandan Babu R
2022-01-07 19:03 ` Darrick J. Wong
2022-01-08 16:16 ` Chandan Babu R
2022-01-08 18:28 ` Darrick J. Wong
2022-01-10 15:42 ` Chandan Babu R
2021-12-14 8:48 ` [PATCH V4 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=20220105011731.GF656707@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 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).