From: Brian Foster <bfoster@redhat.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org,
djwong@kernel.org, hch@lst.de
Subject: Re: [PATCH 1/2] xfs: online grow vs. log recovery stress test
Date: Tue, 29 Oct 2024 10:22:52 -0400 [thread overview]
Message-ID: <ZyDvvN5CGHaEOyaW@bfoster> (raw)
In-Reply-To: <20241025173242.clzuckwfotkdkpwq@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On Sat, Oct 26, 2024 at 01:32:42AM +0800, Zorro Lang wrote:
> On Thu, Oct 17, 2024 at 12:34:04PM -0400, Brian Foster wrote:
> > fstests includes decent functional tests for online growfs and
> > shrink, and decent stress tests for crash and log recovery, but no
> > combination of the two. This test combines bits from a typical
> > growfs stress test like xfs/104 with crash recovery cycles from a
> > test like generic/388. As a result, this reproduces at least a
> > couple recently fixed issues related to log recovery of online
> > growfs operations.
> >
> > Signed-off-by: Brian Foster <bfoster@redhat.com>
> > ---
>
> Hi Brian,
>
> Thanks for this new test case! Some tiny review points below :)
>
> > tests/xfs/609 | 69 +++++++++++++++++++++++++++++++++++++++++++++++
> > tests/xfs/609.out | 7 +++++
> > 2 files changed, 76 insertions(+)
> > create mode 100755 tests/xfs/609
> > create mode 100644 tests/xfs/609.out
> >
...
> > diff --git a/tests/xfs/609.out b/tests/xfs/609.out
> > new file mode 100644
> > index 00000000..1853cc65
> > --- /dev/null
> > +++ b/tests/xfs/609.out
> > @@ -0,0 +1,7 @@
> > +QA output created by 609
> > +meta-data=DDEV isize=XXX agcount=N, agsize=XXX blks
> > +data = bsize=XXX blocks=XXX, imaxpct=PCT
> > + = sunit=XXX swidth=XXX, unwritten=X
> > +naming =VERN bsize=XXX
> > +log =LDEV bsize=XXX blocks=XXX
> > +realtime =RDEV extsz=XXX blocks=XXX, rtextents=XXX
>
> So what's this output in .out file for? How about "Silence is golden"?
>
No particular reason.. this was mostly a mash and cleanup of a couple
preexisting tests around growfs and crash recovery, so probably just
leftover from that. All of these suggestions sound good to me. I'll
apply them and post a v2. Thanks for the review!
Brian
> Thanks,
> Zorro
>
> > --
> > 2.46.2
> >
> >
>
next prev parent reply other threads:[~2024-10-29 14:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 16:34 [PATCH 0/2] fstests/xfs: a couple growfs log recovery tests Brian Foster
2024-10-17 16:34 ` [PATCH 1/2] xfs: online grow vs. log recovery stress test Brian Foster
2024-10-25 17:32 ` Zorro Lang
2024-10-29 14:22 ` Brian Foster [this message]
2024-10-17 16:34 ` [PATCH 2/2] xfs: online grow vs. log recovery stress test (realtime version) Brian Foster
2024-10-18 5:09 ` [PATCH 0/2] fstests/xfs: a couple growfs log recovery tests Christoph Hellwig
2024-10-18 11:29 ` Brian Foster
2024-10-18 21:39 ` Darrick J. Wong
2024-10-21 16:41 ` Darrick J. Wong
2024-10-22 5:52 ` Christoph Hellwig
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=ZyDvvN5CGHaEOyaW@bfoster \
--to=bfoster@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--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