From: John Garry <john.g.garry@oracle.com>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>,
Zorro Lang <zlang@redhat.com>,
fstests@vger.kernel.org
Cc: Ritesh Harjani <ritesh.list@gmail.com>, djwong@kernel.org, tytso@mit.edu
Subject: Re: [PATCH v2 05/13] generic/1226: Add atomic write test using fio crc check verifier
Date: Fri, 27 Jun 2025 15:09:09 +0100 [thread overview]
Message-ID: <0430bd73-e6c2-4ce9-af24-67b1e1fa9b5b@oracle.com> (raw)
In-Reply-To: <227ca6650cf5ef5a9a3383a06cd08c0c2b9f43c3.1750924903.git.ojaswin@linux.ibm.com>
> +touch "$SCRATCH_MNT/f1"
> +awu_min_write=$(_get_atomic_write_unit_min "$SCRATCH_MNT/f1")
> +awu_max_write=$(_get_atomic_write_unit_max "$SCRATCH_MNT/f1")
> +blocksize=$(_max "$awu_min_write" "$((awu_max_write/2))")
> +
> +# XFS can have high awu_max_write due to software fallback. Cap it at 64k
This test fails on xfs due for this reason. software fallback -based
atomic writes have no serialization against reads or other writes.
Can you cap at atomic write unit max opt? That will mean that we get
serialization from atomic write HW support.
BTW, to repeat what I said before, it can also fail for atomic write
bios using HW support, as reads may be split.
See this sample output:
generic/1226 68s ... - output mismatch (see
/home/opc/xfstests-dev/results//generic/1226.out.bad)
--- tests/generic/1226.out 2025-06-27 11:26:58.411121674 +0000
+++ /home/opc/xfstests-dev/results//generic/1226.out.bad
2025-06-27 14:03:08.933811064 +0000
@@ -1,2 +1,104 @@
QA output created by 1226
+crc32c: verify failed at file /home/opc/mnt/scratch/test-file
offset 16457728, length 8192 (requested block: offset=16457728,
length=8192, flags=84)
+ Expected CRC: 712de900
+ Received CRC: f872a18d
+crc32c: verify failed at file /home/opc/mnt/scratch/test-file
offset 88104960, length 8192 (requested block: offset=88104960,
length=8192, flags=84)
+ Expected CRC: 4aaaf009
+ Received CRC: 2a5770cf
...
(Run 'diff -u /home/opc/xfstests-dev/tests/generic/1226.out
/home/opc/xfstests-dev/results//generic/1226.out.bad' to see the entire
diff)
Ran: generic/1226
Failures: generic/1226
Failed 1 of 1 tests
[root@jgarry-ol9new xfstests-dev]# cat /sys/block/sdi/queue/max_sectors_kb
4
[root@jgarry-ol9new xfstests-dev]#
However, nobody should fiddle with max_sectors_kb, so the test still has
value.
> +blocksize=$(_min "$blocksize" "65536")
> +
> +fio_config=$tmp.fio
> +fio_out=$tmp.fio.out
> +
next prev parent reply other threads:[~2025-06-27 14:09 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 11:58 [PATCH v2 00/13] Add more tests for multi fs block atomic writes Ojaswin Mujoo
2025-06-26 11:58 ` [PATCH v2 01/13] common/rc: Add _min() and _max() helpers Ojaswin Mujoo
2025-06-26 11:58 ` [PATCH v2 02/13] common/rc: Fix fsx for ext4 with bigalloc Ojaswin Mujoo
2025-06-26 13:32 ` Theodore Ts'o
2025-06-30 15:28 ` Darrick J. Wong
2025-07-01 6:26 ` Ojaswin Mujoo
2025-07-02 15:13 ` Darrick J. Wong
2025-06-26 11:58 ` [PATCH v2 03/13] common/rc: Add a helper to run fsx on a given file Ojaswin Mujoo
2025-06-26 11:58 ` [PATCH v2 04/13] ltp/fsx.c: Add atomic writes support to fsx Ojaswin Mujoo
2025-06-26 11:58 ` [PATCH v2 05/13] generic/1226: Add atomic write test using fio crc check verifier Ojaswin Mujoo
2025-06-27 14:09 ` John Garry [this message]
2025-07-01 16:18 ` Ojaswin Mujoo
2025-07-02 7:46 ` John Garry
2025-07-03 6:42 ` Ojaswin Mujoo
2025-07-03 16:26 ` John Garry
2025-07-04 14:35 ` Ojaswin Mujoo
2025-07-04 15:23 ` Ojaswin Mujoo
2025-07-07 8:18 ` John Garry
2025-07-08 6:50 ` Ojaswin Mujoo
2025-07-08 11:11 ` John Garry
2025-07-08 12:01 ` Ojaswin Mujoo
2025-07-08 12:34 ` John Garry
2025-07-11 10:39 ` Ojaswin Mujoo
2025-07-11 10:51 ` John Garry
2025-07-11 18:16 ` Ojaswin Mujoo
2025-07-07 8:02 ` John Garry
2025-06-26 11:58 ` [PATCH v2 06/13] generic/1227: Add atomic write test using fio verify on file mixed mappings Ojaswin Mujoo
2025-06-27 14:48 ` John Garry
2025-06-26 11:58 ` [PATCH v2 07/13] generic/1228: Add atomic write multi-fsblock O_[D]SYNC tests Ojaswin Mujoo
2025-06-26 11:58 ` [PATCH v2 08/13] generic/1229: Stress fsx with atomic writes enabled Ojaswin Mujoo
2025-06-26 11:59 ` [PATCH v2 09/13] generic/1230: Add sudden shutdown tests for multi block atomic writes Ojaswin Mujoo
2025-06-27 16:11 ` John Garry
2025-07-01 6:34 ` Ojaswin Mujoo
2025-06-26 11:59 ` [PATCH v2 10/13] ext4/061: Atomic writes stress test for bigalloc using fio crc verifier Ojaswin Mujoo
2025-06-26 11:59 ` [PATCH v2 11/13] ext4/062: Atomic writes test for bigalloc using fio crc verifier on multiple files Ojaswin Mujoo
2025-06-26 11:59 ` [PATCH v2 12/13] ext4/063: Atomic write test for extent split across leaf nodes Ojaswin Mujoo
2025-06-26 11:59 ` [PATCH v2 13/13] ext4/064: Add atomic write tests for journal credit calculation Ojaswin Mujoo
2025-06-27 13:56 ` [PATCH v2 00/13] Add more tests for multi fs block atomic writes John Garry
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=0430bd73-e6c2-4ce9-af24-67b1e1fa9b5b@oracle.com \
--to=john.g.garry@oracle.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--cc=zlang@redhat.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