From: "Darrick J. Wong" <djwong@kernel.org>
To: Gao Xiang <hsiangkao@redhat.com>
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org,
Zorro Lang <zlang@redhat.com>, Eryu Guan <guan@eryu.me>
Subject: Re: [PATCH v4 1/3] common/xfs: add _require_xfs_scratch_shrink helper
Date: Mon, 10 May 2021 10:59:52 -0700 [thread overview]
Message-ID: <20210510175952.GA8558@magnolia> (raw)
In-Reply-To: <20210402094937.4072606-2-hsiangkao@redhat.com>
On Fri, Apr 02, 2021 at 05:49:35PM +0800, Gao Xiang wrote:
> In order to detect whether the current kernel supports XFS shrinking.
>
> Signed-off-by: Gao Xiang <hsiangkao@redhat.com>
> ---
> common/xfs | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/common/xfs b/common/xfs
> index 69f76d6e..c6c2e3f5 100644
> --- a/common/xfs
> +++ b/common/xfs
> @@ -766,6 +766,20 @@ _require_xfs_mkfs_without_validation()
> fi
> }
>
> +_require_xfs_scratch_shrink()
> +{
> + _require_scratch
> + _require_command "$XFS_GROWFS_PROG" xfs_growfs
> +
> + _scratch_mkfs_xfs | _filter_mkfs 2>$tmp.mkfs >/dev/null
> + . $tmp.mkfs
> + _scratch_mount
> + # here just to check if kernel supports, no need do more extra work
> + $XFS_GROWFS_PROG -D$((dblocks-1)) "$SCRATCH_MNT" > /dev/null 2>&1 || \
> + _notrun "kernel does not support shrinking"
I think isn't sufficiently precise -- if xfs_growfs (userspace) doesn't
support shrinking it'll error out with "data size XXX too small", and if
the kernel doesn't support shrink, it'll return EINVAL.
As written, this code attempts a single-block shrink and disables the
entire test if that fails for any reason, even if that reason is that
the last block in the filesystem isn't free, or we ran out of memory, or
something like that.
I think this needs to check the output of xfs_growfs to make the
decision to _notrun.
--D
> + _scratch_unmount
> +}
> +
> # XFS ability to change UUIDs on V5/CRC filesystems
> #
> _require_meta_uuid()
> --
> 2.27.0
>
next prev parent reply other threads:[~2021-05-10 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 9:49 [PATCH v4 0/3] xfs: testcases for shrinking free space in the last AG Gao Xiang
2021-04-02 9:49 ` [PATCH v4 1/3] common/xfs: add _require_xfs_scratch_shrink helper Gao Xiang
2021-05-10 17:59 ` Darrick J. Wong [this message]
2021-05-11 2:02 ` Gao Xiang
2021-05-11 2:34 ` Darrick J. Wong
2021-04-02 9:49 ` [PATCH v4 2/3] xfs: basic functionality test for shrinking free space in the last AG Gao Xiang
2021-05-10 18:01 ` Darrick J. Wong
2021-05-11 2:04 ` Gao Xiang
2021-04-02 9:49 ` [PATCH v4 3/3] xfs: stress " Gao Xiang
2021-05-10 18:08 ` Darrick J. Wong
2021-05-11 2:19 ` Gao Xiang
2021-05-10 11:18 ` [PATCH v4 0/3] xfs: testcases " Gao Xiang
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=20210510175952.GA8558@magnolia \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=hsiangkao@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.com \
/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).