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 08:52:40 +0000 [thread overview]
Message-ID: <c5cff4c3-cf0a-47cc-9ae5-20d7316b3c09@oracle.com> (raw)
In-Reply-To: <mx6gzhhkvcdnadmmxziu77cuywq4ql5u2hp6fd673vorhx35pz@jmyv74f236ka>
On 05/11/2025 02:19, Shinichiro Kawasaki wrote:
> On Nov 04, 2025 / 16:33, Darrick J. Wong wrote:
>> [add jogarry/ojaswin since this is a new atomic writes test]
>>
>> On Thu, Oct 30, 2025 at 08:45:05AM +0000, Shinichiro Kawasaki wrote:
>>> I observe the fstests test case generic/774 hangs, when I run it for xfs on 8GiB
>>> TCMU fileio devices. It was observed with v6.17 and v6.18-rcX kernel versions.
>>> FYI, here I attach the kernel message log that was taken with v6.18-rc3 kernel
>>> [1]. The hang is recreated in stable manner by repeating the test case a few
>>> times in my environment.
>>>
>>> Actions for fix will be appreciated. If I can do any help, please let me know.
>>
>> I wonder, does your disk support atomic writes or are we just using the
>> software fallback in xfs?
>
> I don't think the disk supports atomic writes. It is just a regular TCMU device,
> and its atomic write related sysfs attributes have value 0:
>
> $ grep -rne . /sys/block/sdh/queue/ | grep atomic
> /sys/block/sdh/queue/atomic_write_unit_max_bytes:1:0
> /sys/block/sdh/queue/atomic_write_boundary_bytes:1:0
> /sys/block/sdh/queue/atomic_write_max_bytes:1:0
> /sys/block/sdh/queue/atomic_write_unit_min_bytes:1:0
>
> FYI, I attach the all sysfs queue attribute values of the device [2].
Yes, this would only be using software-based atomic writes.
Shinichiro, do the other atomic writes tests run ok, like 775, 767? You
can check group "atomicwrites" to know which tests they are.
774 is the fio test.
Some things to try:
- use a physical disk for the TEST_DEV
- Don't set LOAD_FACTOR (if you were setting it). If not, bodge 774 to
reduce $threads to a low value, say, 2
- trying turning on XFS_DEBUG config
BTW, Darrick has posted some xfs atomics fixes @
https://lore.kernel.org/linux-xfs/20251105001200.GV196370@frogsfrogsfrogs/T/#t.
I doubt that they will help this, but worth trying.
I will try to recreate.
Thanks,
John
next prev parent reply other threads:[~2025-11-05 8:52 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 [this message]
2025-11-05 10:39 ` John Garry
2025-11-05 11:29 ` John Garry
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=c5cff4c3-cf0a-47cc-9ae5-20d7316b3c09@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