From: John Garry <john.g.garry@oracle.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
"Darrick J. Wong" <djwong@kernel.org>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"ojaswin@linux.ibm.com" <ojaswin@linux.ibm.com>
Subject: Re: [bug report] fstests generic/774 hang
Date: Wed, 5 Nov 2025 11:29:05 +0000 [thread overview]
Message-ID: <728dcb65-764f-4b25-92ca-9d55d4dc4ab7@oracle.com> (raw)
In-Reply-To: <2c4d144b-81fd-4e4c-90a8-fd3c2082246c@oracle.com>
On 05/11/2025 10:39, John Garry wrote:
>
> +fio: failed initializing LFSR
> +fio: failed initializing LFSR
> +fio: failed initializing LFSR
> +fio: failed initializing LFSR
> +verify: bad magic header 0, wanted acca at file /home/ubuntu/mnt/
> scratch/test-file offset 0, length 1048576 (requested block: offset=0,
> length=1048576)
> +verify: bad magic header e3d6, wanted acca at file /home/ubuntu/
> mnt/scratch/test-file offset 8388608, length 1048576 (requested block:
> offset=8388608, length=1048576)
>
> I need to check that fio complaint.
This issue goes away when I stop using lfsr, i.e. the test passes.
The problem is that lfsr init in fio does not have enough "blocks", and
this comes from how the fio bs is same as the increment aw_io_inc, both
1M in my case. I think that aw_io_inc needs to be much lager than bs.
BTW, I think that the random number gen fio param is only relevant in
fio write mode. It seems to be even set in 774 for verify read.
Thanks,
John
next prev parent reply other threads:[~2025-11-05 11:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 8:45 [bug report] fstests generic/774 hang Shinichiro Kawasaki
2025-11-05 0:33 ` Darrick J. Wong
2025-11-05 2:19 ` Shinichiro Kawasaki
2025-11-05 8:52 ` John Garry
2025-11-05 10:39 ` John Garry
2025-11-05 11:29 ` John Garry [this message]
2025-11-05 12:37 ` Shinichiro Kawasaki
2025-11-06 8:19 ` Shinichiro Kawasaki
2025-11-06 8:53 ` John Garry
2025-11-07 2:27 ` Shinichiro Kawasaki
2025-11-07 4:28 ` Darrick J. Wong
2025-11-07 5:53 ` Shinichiro Kawasaki
2025-11-07 12:48 ` John Garry
2025-11-07 17:50 ` Darrick J. Wong
2025-11-07 23:18 ` Darrick J. Wong
2025-11-10 2:41 ` Shinichiro Kawasaki
2025-11-09 12:02 ` Ojaswin Mujoo
2025-11-10 12:46 ` [WARNING: UNSCANNABLE EXTRACTION FAILED]Re: " Shinichiro Kawasaki
2025-11-10 21:12 ` Darrick J. Wong
2025-11-11 11:43 ` Shinichiro Kawasaki
2025-11-09 11:58 ` Ojaswin Mujoo
2025-11-10 8:58 ` John Garry
2025-11-10 12:39 ` Shinichiro Kawasaki
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=728dcb65-764f-4b25-92ca-9d55d4dc4ab7@oracle.com \
--to=john.g.garry@oracle.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=shinichiro.kawasaki@wdc.com \
/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