From: Jens Axboe <axboe@kernel.dk>
To: Theodore Ts'o <tytso@mit.edu>, fstests@vger.kernel.org
Subject: Re: xfstests flakiness in generic/095 triggered by fio 3.37
Date: Mon, 15 Apr 2024 12:26:34 -0600 [thread overview]
Message-ID: <a8f03f2c-5951-4aea-856b-218326815302@kernel.dk> (raw)
In-Reply-To: <20240415182231.GA2649469@mit.edu>
On 4/15/24 12:22 PM, Theodore Ts'o wrote:
> I was updating various components in my xfstests test appliance, and
> it appears that fio 3.37 is causing generic/095 to become flaky.
> Previously, I had been using fio 3.35 and a quick test shows that fio
> 3.36 seems to be OK. So the change seems to be somethinig that was
> introduced between fio 3.36 and 3.37.
>
> The test failures seem to be caused by the following unexpected
> message in the output file:
>
> fio: first I/O failed. If /xt-vdc/file1 is a zoned block device, consider --zonemode=zbd
>
> The following comment in tests/generic/095 suggests to my suspicious
> mind that the above warning message isn't getting suppressed when
> --ignore_error=,EIO is passed to fio:
>
> # There's a known EIO failure to report collisions between directio and buffered
> # writes to userspace, refer to upstream linux 5a9d929d6e13. So ignore EIO error
> # at here.
>
> .... but I could be wrong about that.
>
> For now, I've just switched to using fio 3.36, since there's nothing
> in my testing that really _requires_ 3.37. It might be that we should
> just work around this by filtering out the warning message in
> xfstests. Or maybe we should make a change in fio?
I'll just revert that change, not sure how it slipped by that it also
change it from informational to an error message.
--
Jens Axboe
prev parent reply other threads:[~2024-04-15 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 18:22 xfstests flakiness in generic/095 triggered by fio 3.37 Theodore Ts'o
2024-04-15 18:26 ` Jens Axboe [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=a8f03f2c-5951-4aea-856b-218326815302@kernel.dk \
--to=axboe@kernel.dk \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).