public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: fstests@vger.kernel.org
Cc: linux-xfs@vger.kernel.org, djwong@kernel.org, hch@lst.de
Subject: [PATCH 0/2] fstests/xfs: a couple growfs log recovery tests
Date: Thu, 17 Oct 2024 12:34:03 -0400	[thread overview]
Message-ID: <20241017163405.173062-1-bfoster@redhat.com> (raw)

Hi all,

This is first pass of a growfs crash and log recovery test I cooked up
for XFS. A bit more background and context on this is available here
[1]. In short, this reproduces at least a couple log recovery issues on
XFS related to growfs that Christoph has tracked down and resolved.
Darrick proposed a simple realtime variant in the discussion at [1], so
patch 2 is a stab at that. It's basically just a copy of patch 1 with
some rt related tweaks. However..

Darrick,

I believe you reproduced a problem with your customized realtime variant
of the initial test. I've not been able to reproduce any test failures
with patch 2 here, though I have tried to streamline the test a bit to
reduce unnecessary bits (patch 1 still reproduces the original
problems). I also don't tend to test much with rt, so it's possible my
config is off somehow or another. Otherwise I _think_ I've included the
necessary changes for rt support in the test itself.

Thoughts? I'd like to figure out what might be going on there before
this should land..

Brian

[1] https://lore.kernel.org/fstests/20240910043127.3480554-1-hch@lst.de/

Brian Foster (2):
  xfs: online grow vs. log recovery stress test
  xfs: online grow vs. log recovery stress test (realtime version)

 tests/xfs/609     | 69 +++++++++++++++++++++++++++++++++++++++++++++
 tests/xfs/609.out |  7 +++++
 tests/xfs/610     | 71 +++++++++++++++++++++++++++++++++++++++++++++++
 tests/xfs/610.out |  7 +++++
 4 files changed, 154 insertions(+)
 create mode 100755 tests/xfs/609
 create mode 100644 tests/xfs/609.out
 create mode 100755 tests/xfs/610
 create mode 100644 tests/xfs/610.out

-- 
2.46.2


             reply	other threads:[~2024-10-17 16:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17 16:34 Brian Foster [this message]
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
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=20241017163405.173062-1-bfoster@redhat.com \
    --to=bfoster@redhat.com \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --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