All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Su Yue <damenly.su@gmail.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>, fstests@vger.kernel.org
Subject: Re: [PATCH] generic: test which tries to exercise AIO/DIO into unwritten space
Date: Wed, 3 Mar 2021 15:02:00 -0500	[thread overview]
Message-ID: <YD/rONmSSOgDV644@mit.edu> (raw)
In-Reply-To: <CABnRu57hdKav3Mi8vQYeowZrQtFToMSzK23h4H2DuqGL0Dea2A@mail.gmail.com>

On Tue, Mar 02, 2021 at 11:20:06AM +0800, Su Yue wrote:
> But both xfs and ext4 100% fail in v5.12-rc1 with 4k block size and 4k page
> size on x86_64. The test itself should be okay because btrfs passes.
> xfstests-dev version is 8cbc48b460b6 applied this patch. logs are attached.

Hmm, interesting.  Thanks for the report.  I've been running most of
my tests on a GCE VVM (using gce-xfstests) with a 100GB PD-SSD as the
storage device.  I just tried, and it's passing now reliably on both
4k and 1k for me, both on v5.11 and v5.12-rc1.  (Previously it was
failing about 30% of the time on the ext4/1k test scenario, and was
passing 100% on ext4/4k.)

Given your report, I tried running it using KVM (with a NVME ssd as
the back-end storage device), and it's failing 80% of the time using
the 4k block size.

So previously I had assumed that it was passing consistently on with
ext4/4k, but it looks like that it's very much dependent on the
performance of the TEST_DEV.

					- Ted

  parent reply	other threads:[~2021-03-04  0:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 20:58 [PATCH] generic: test which tries to exercise AIO/DIO into unwritten space Theodore Ts'o
2021-03-01 17:02 ` Theodore Ts'o
2021-03-01 17:14 ` Darrick J. Wong
2021-03-01 18:04   ` Theodore Ts'o
     [not found]     ` <CABnRu57hdKav3Mi8vQYeowZrQtFToMSzK23h4H2DuqGL0Dea2A@mail.gmail.com>
2021-03-02  3:33       ` Darrick J. Wong
2021-03-02  4:25         ` Su Yue
2021-03-03 20:02       ` Theodore Ts'o [this message]
2021-03-07 16:24 ` Eryu Guan
2021-03-07 23:11   ` Theodore Ts'o
2021-03-08  1:22     ` [PATCH -v2] " Theodore Ts'o
2021-03-15 21:10       ` Darrick J. Wong

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=YD/rONmSSOgDV644@mit.edu \
    --to=tytso@mit.edu \
    --cc=damenly.su@gmail.com \
    --cc=djwong@kernel.org \
    --cc=fstests@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 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.