From: "Theodore Ts'o" <tytso@mit.edu>
To: Luis Henriques <lhenriques@suse.de>
Cc: Jens Axboe <axboe@kernel.dk>,
fstests@vger.kernel.org, fio@vger.kernel.org
Subject: Re: generic/095 failing in ext4 and xfs
Date: Mon, 4 Oct 2021 12:18:24 -0400 [thread overview]
Message-ID: <YVspUJUSk1gB23JK@mit.edu> (raw)
In-Reply-To: <YVrwvqOiI6CMpq2X@suse.de>
On Mon, Oct 04, 2021 at 01:17:02PM +0100, Luis Henriques wrote:
>
> Ok, I may have narrowed it a bit more. The disks being used in my testing
> were zram-based (I know, I should have mentioned it before :-/ ). If I use
> file-based disks the test passes and I see no crashes in fio.
What was the last kernel version where it didn't crash for you? 5.14?
And maybe we need to have a test which explicitly uses zram, since I
suspect many/most of the fs developers who are running fstests aren't
using zram....
- Ted
next prev parent reply other threads:[~2021-10-04 16:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 17:11 generic/095 failing in ext4 and xfs Luis Henriques
2021-10-01 20:07 ` Theodore Ts'o
2021-10-01 20:46 ` Jens Axboe
2021-10-01 21:59 ` Theodore Ts'o
2021-10-02 10:16 ` Luis Henriques
2021-10-02 14:59 ` Jens Axboe
2021-10-04 10:08 ` Luis Henriques
2021-10-04 10:15 ` Luis Henriques
2021-10-04 12:17 ` Luis Henriques
2021-10-04 16:18 ` Theodore Ts'o [this message]
2021-10-06 13:39 ` Luis Henriques
2021-10-11 10:27 ` [PATCH] fio: make sure io_u->file isn't NULL before using it Luís Henriques
2021-10-11 12:58 ` Jens Axboe
2021-10-11 13:44 ` Luís Henriques
2021-10-11 15:15 ` Jens Axboe
2021-10-11 15:45 ` Luís Henriques
2021-10-10 8:31 ` generic/095 failing in ext4 and xfs Zorro Lang
2021-10-11 9:09 ` Luís Henriques
2021-10-11 9:31 ` Ming Lei
2021-10-11 10:16 ` Luís Henriques
2021-10-11 11:13 ` Ming Lei
2021-10-11 13:41 ` Luís Henriques
2021-10-11 12:44 ` Theodore Ts'o
2021-10-11 13:41 ` Luís Henriques
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=YVspUJUSk1gB23JK@mit.edu \
--to=tytso@mit.edu \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=fstests@vger.kernel.org \
--cc=lhenriques@suse.de \
/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.