FS/XFS testing framework
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 4/4] generic/475: skip test when using an external log device
Date: Wed, 20 Jul 2022 11:29:27 -0700	[thread overview]
Message-ID: <YthJh1RPO6nbgfPv@magnolia> (raw)
In-Reply-To: <20220720164356.4078789-5-tytso@mit.edu>

On Wed, Jul 20, 2022 at 12:43:56PM -0400, Theodore Ts'o wrote:
> This test tests log recovery by kicking off fstress on the scratch fs,
> then switching out the underlying the device with dm-error to see what
> happens when the disk goes down.  But when there is an external log
> device writes to the log device still succeed, while writes to the
> rest of the file system fail, and this leads to file system
> corruption.  So skip this test when there is an external log.

Hm, could you review the congruent operation length series[1], please?

Once that's done, I can move on to the next push, which is fixing up
dmerror[2] and fail-make-request[3] to handle external devices:

[1] https://lore.kernel.org/fstests/165826663647.3249494.13640199673218669145.stgit@magnolia/T/#t
[2] https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfstests-dev.git/log/?h=dmerror-on-rt-devices
[3] https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfstests-dev.git/log/?h=fix-fail-make-reqest

--D

> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> ---
>  tests/generic/475 | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/tests/generic/475 b/tests/generic/475
> index c426402e..43c26303 100755
> --- a/tests/generic/475
> +++ b/tests/generic/475
> @@ -34,6 +34,10 @@ _require_scratch
>  _require_dm_target error
>  _require_command "$KILLALL_PROG" "killall"
>  
> +if test "$USE_EXTERNAL" = yes -a ! -z "$SCRATCH_LOGDEV" ; then
> +    _notrun "Cannot have external log device"
> +fi
> +
>  echo "Silence is golden."
>  
>  _scratch_mkfs >> $seqres.full 2>&1
> -- 
> 2.31.0
> 

      reply	other threads:[~2022-07-20 18:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20 16:43 [PATCH 0/4] fstests: more random fixes from Ted Theodore Ts'o
2022-07-20 16:43 ` [PATCH 1/4] report: add support for the xunit-quiet format Theodore Ts'o
2022-07-20 18:35   ` Darrick J. Wong
2022-07-20 16:43 ` [PATCH 2/4] generic/556: add a check to make sure ext4 supports encrypted casefolding Theodore Ts'o
2022-07-21  2:40   ` Eric Biggers
2022-07-20 16:43 ` [PATCH 3/4] dmflakey: don't run dmflakey tests with an external log device Theodore Ts'o
2022-07-20 17:35   ` Darrick J. Wong
2022-07-20 16:43 ` [PATCH 4/4] generic/475: skip test when using " Theodore Ts'o
2022-07-20 18:29   ` Darrick J. Wong [this message]

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=YthJh1RPO6nbgfPv@magnolia \
    --to=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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