From: Gao Xiang <hsiangkao@redhat.com>
To: linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Zorro Lang <zlang@redhat.com>, Eryu Guan <guan@eryu.me>,
Gao Xiang <hsiangkao@redhat.com>
Subject: [PATCH v4 0/3] xfs: testcases for shrinking free space in the last AG
Date: Fri, 2 Apr 2021 17:49:34 +0800 [thread overview]
Message-ID: <20210402094937.4072606-1-hsiangkao@redhat.com> (raw)
Hi,
Sorry for little delay (yet since xfsprogs side isn't merged, and no
major changes compared with the previous version...)
This version matches
kernel: for-next
xfsprogs: https://lore.kernel.org/r/20210326024631.12921-1-hsiangkao@aol.com
and mainly addresses comments for the previous version (but note I don't
tend to dump shrink information but rather confirm the final state runtimely,
since blocksize needs to be fixed and output could change by time, so just
need to confirm xfs_repair can pass and final dblocks is what we want.)
Thanks,
Gao Xinag
changes since RFC v3 (Eryu):
- [1/3] rename to _require_xfs_scratch_shrink;
- [1/3] add growfs command check;
- [1/3] try to shrink 1 dblock to check kernel support instead;
- [2/3] use _check_scratch_fs instead;
- [2/3] add comment on why agcount=3;
- [2/3] add shrinkfs group;
- [3/3] use _scratch_mount;
- [3/3] Declare variables in stress_scratch() as local;
- [3/3] run stress_scratch() in background;
Gao Xiang (3):
common/xfs: add _require_xfs_scratch_shrink helper
xfs: basic functionality test for shrinking free space in the last AG
xfs: stress test for shrinking free space in the last AG
common/xfs | 14 ++++++
tests/xfs/990 | 73 ++++++++++++++++++++++++++++
tests/xfs/990.out | 12 +++++
tests/xfs/991 | 118 ++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/991.out | 8 ++++
tests/xfs/group | 2 +
6 files changed, 227 insertions(+)
create mode 100755 tests/xfs/990
create mode 100644 tests/xfs/990.out
create mode 100755 tests/xfs/991
create mode 100644 tests/xfs/991.out
--
2.27.0
next reply other threads:[~2021-04-02 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 9:49 Gao Xiang [this message]
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
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=20210402094937.4072606-1-hsiangkao@redhat.com \
--to=hsiangkao@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--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 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.