Linux XFS filesystem development
 help / color / mirror / Atom feed
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 10:39:43 +0000	[thread overview]
Message-ID: <2c4d144b-81fd-4e4c-90a8-fd3c2082246c@oracle.com> (raw)
In-Reply-To: <c5cff4c3-cf0a-47cc-9ae5-20d7316b3c09@oracle.com>

On 05/11/2025 08:52, John Garry wrote:
>> 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://urldefense.com/ 
> v3/__https://lore.kernel.org/linux- 
> xfs/20251105001200.GV196370@frogsfrogsfrogs/T/*t__;Iw!!ACWV5N9M2RV99hQ! 
> IuEPY6yJ1ZEQu7dpfjUplkPJucOHMQ9cpPvIC4fiJhTi_X_7ImN0t6wGqxg9_GM6gWe4B1OBiBjEI8Gz_At0595tIQ$ . I doubt that they will help this, but worth trying.
> 
> I will try to recreate.

I tested this and the filesize which we try to write is huge, like 3.3G 
in my case. That seems excessive.

The calc comes from the following in 774:

filesize=$((aw_bsize * threads * 100))

aw_bsize for  me is 1M, and threads is 32

aw_bsize is large as XFS supports software-based atomics, which is 
generally going to be huge compared to anything which HW can support.

When I tried to run this test, it was not completing in a sane amount of 
time - it was taking many minutes before I gave up.

@shinichiro, please try this:

--- a/tests/generic/774
+++ b/tests/generic/774
@@ -29,7 +29,7 @@ aw_bsize=$(_max "$awu_min_write" "$((awu_max_write/4))")
  fsbsize=$(_get_block_size $SCRATCH_MNT)

  threads=$(_min "$(($(nproc) * 2 * LOAD_FACTOR))" "100")
-filesize=$((aw_bsize * threads * 100))
+filesize=$((aw_bsize * threads))
  depth=$threads
  aw_io_size=$((filesize / threads))
  aw_io_inc=$aw_io_size
ubuntu@jgarry-instance-20240626-1657-xfs-ubuntu:~/xfstests-dev$


Note, I ran with this change and the test now completes, but I get this:

+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.

Thanks,
John

  reply	other threads:[~2025-11-05 10:39 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 [this message]
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=2c4d144b-81fd-4e4c-90a8-fd3c2082246c@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