From: Gao Xiang <hsiangkao@redhat.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [WIP] [RFC PATCH] xfs: add test on shrinking unused space in the last AG
Date: Wed, 10 Mar 2021 10:33:53 +0800 [thread overview]
Message-ID: <20210310023353.GC4003044@xiangao.remote.csb> (raw)
In-Reply-To: <20210310020947.GC3419940@magnolia>
Hi Darrick,
On Tue, Mar 09, 2021 at 06:09:47PM -0800, Darrick J. Wong wrote:
...
> >
> > As Darrick has reviewed, I have one more question. Looks like we can shrink a
> > mounted xfs via giving a smaller size to xfs_growfs.
> >
> > If xfs_growfs or kernel doesn't support 'shrink', I think the whole test will
> > be failed. So maybe we need a _require_* function to check if current xfs
> > support shrinking feature at first?
>
> Also, it's time to send the xfs_growfs patches to the list so I can
> replicate the tests on my own test vms.
There was a preliminary version of xfsprogs sent out before to
match this version:
https://lore.kernel.org/r/20201028114010.545331-1-hsiangkao@redhat.com
https://lore.kernel.org/linux-xfs/20201028114010.545331-1-hsiangkao@redhat.com/raw
This added a EXPERIMENTAL warning but without a new argument
for shrinking.
Thanks,
Gao Xiang
next prev parent reply other threads:[~2021-03-10 2:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 23:09 [WIP] [RFC PATCH] xfs: add test on shrinking unused space in the last AG Gao Xiang
2021-03-09 18:03 ` Darrick J. Wong
2021-03-10 2:07 ` Gao Xiang
2021-03-10 2:19 ` Darrick J. Wong
2021-03-10 0:43 ` Zorro Lang
2021-03-10 2:09 ` Darrick J. Wong
2021-03-10 2:33 ` Gao Xiang [this message]
2021-03-10 2:16 ` Gao Xiang
-- strict thread matches above, loose matches on Subject: below --
2020-10-28 11:30 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=20210310023353.GC4003044@xiangao.remote.csb \
--to=hsiangkao@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--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