From: "Luís Henriques" <lhenriques@suse.de>
To: fstests@vger.kernel.org, fio@vger.kernel.org
Subject: Re: generic/095 failing in ext4 and xfs
Date: Mon, 11 Oct 2021 10:09:30 +0100 [thread overview]
Message-ID: <YWP/SmhG8TviBE2w@suse.de> (raw)
In-Reply-To: <20211010083125.dne6pcjjboixdllo@fedora>
On Sun, Oct 10, 2021 at 04:31:25PM +0800, Zorro Lang wrote:
> On Fri, Oct 01, 2021 at 06:11:49PM +0100, Luis Henriques wrote:
> > Hi!
> >
> > I'm seeing generic/095 failing both with ext4 and xfs (but not on btrfs).
> > Here's what I'm getting:
> >
> > # cat results/generic/095.out.bad
> > QA output created by 095
> > fio: io_u error on file /tmp/mnt/scratch/file1: Invalid argument: read offset=51200, buflen=1024
> > fio: io_u error on file /tmp/mnt/scratch/file1: Invalid argument: read offset=133120, buflen=1024
> > fio: io_u error on file /tmp/mnt/scratch/file2: Invalid argument: write offset=92160, buflen=1024
> > fio: io_u error on file /tmp/mnt/scratch/file2: Invalid argument: write offset=158720, buflen=1024
> > fio: io_u error on file /tmp/mnt/scratch/file2: Invalid argument: write offset=513024, buflen=1024
> > fio: io_u error on file /tmp/mnt/scratch/file2: Invalid argument: write offset=33792, buflen=1024
> > fio: io_u error on file /tmp/mnt/scratch/file2: Invalid argument: write offset=449536, buflen=1024
> > fio: io_u error on file /tmp/mnt/scratch/file1: Invalid argument: read offset=45056, buflen=1024
> > fio: io_u error on file /tmp/mnt/scratch/file1: Invalid argument: read offset=30720, buflen=1024
> > fio: io_u error on file /tmp/mnt/scratch/file1: Invalid argument: write offset=222208, buflen=1024
> > fio: io_u error on file /tmp/mnt/scratch/file1: Invalid argument: read offset=342016, buflen=1024
> > fio: io_u error on file /tmp/mnt/scratch/file1: Invalid argument: write offset=177152, buflen=1024
> > fio: pid=4090, got signal=11
> > fio: io_u error on file /tmp/mnt/scratch/file1: Invalid argument: write offset=43008, buflen=1024
> > fio: io_u error on file /tmp/mnt/scratch/file1: Invalid argument: write offset=308224, buflen=1024
> > fio: pid=4086, got signal=11
>
> I *guess* it might be caused by a striped storage(fs) of you?
I'm not sure I understand what you mean by that. As I mentioned somewhere
else in this thread, I'm using zram devices for testing. If I change the
test to use file-backed storage device instead, it passes without any
issues.
Cheers,
--
Luís
>
> Thanks,
> Zorro
>
> > Silence is golden
> >
> > This was for ext4 but the output for xfs is similar. Since fio is getting
> > killed I suspect this may be an issue with this tool. Thus I'm sending
> > this to both fio and fstests mailing-lists.
> >
> > I'm using a 5.15-rc3 kernel and fio-3.28. Is anyone else seeing something
> > similar?
> >
> > Cheers,
> > --
> > Luís
> >
>
next prev parent reply other threads:[~2021-10-11 9:09 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
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 [this message]
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=YWP/SmhG8TviBE2w@suse.de \
--to=lhenriques@suse.de \
--cc=fio@vger.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.