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 09/13] generic/1230: Add sudden shutdown tests for multi block atomic writes
Date: Fri, 27 Jun 2025 17:11:12 +0100 [thread overview]
Message-ID: <b8bd60eb-c926-44f4-a0ff-b5de75803d85@oracle.com> (raw)
In-Reply-To: <eabfa4691ac822af276c900f0cc7502ad62ea768.1750924903.git.ojaswin@linux.ibm.com>
On 26/06/2025 12:59, Ojaswin Mujoo wrote:
> This test is intended to ensure that multi blocks atomic writes
> maintain atomic guarantees across sudden FS shutdowns.
>
> The way we work is that we lay out a file with random mix of written,
> unwritten and hole extents. Then we start performing atomic writes
> sequentially on the file while we parallely shutdown the FS. Then we
> note the last offset where the atomic write happened just before shut
> down and then make sure blocks around it either have completely old
> data or completely new data, ie the write was not torn during shutdown.
>
> We repeat the same with completely written, completely unwritten and completely
> empty file to ensure these cases are not torn either. Finally, we have a
> similar test for append atomic writes
>
> Suggested-by: Ritesh Harjani (IBM)<ritesh.list@gmail.com>
> Signed-off-by: Ojaswin Mujoo<ojaswin@linux.ibm.com>
this seems to work ok for xfs, as I get data verify errors when I remove
the -A arg to xfs_io when doing the atomic writes.
But I see this (always):
@@ -1,2 +1,83 @@
QA output created by 1230
+/home/opc/xfstests-dev/tests/generic/1230: line 13:
_require_scratch_write_atomic_multi_fsblock: command not found
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (535173) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (535256) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (535339) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (535419) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (560146) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (560229) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (560312) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (560392) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (585304) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (585387) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (585470) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (585550) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (610300) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (610384) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (610468) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (610548) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (635276) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (635359) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (635442) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (635523) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (660400) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (660483) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (660566) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (660646) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (685377) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (685460) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (685543) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (685624) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (710361) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (710444) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (710527) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (710607) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (735333) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (735417) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (735500) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (735580) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (760306) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (760390) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (760473) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (760553) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (785276) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (785359) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (785442) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (785522) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (810249) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (810332) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (810415) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (810495) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (835221) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (835304) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (835388) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (835469) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (860199) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (860282) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (860365) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (860445) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (885169) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (885253) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (885336) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (885416) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (910140) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (910223) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (910307) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (910387) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (935110) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (935193) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (935276) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (935356) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (960079) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (960162) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (960245) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (960326) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (985052) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (985135) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (985218) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (985299) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (1010026) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (1010109) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 149: kill: (1010192) -
No such process
+/home/opc/xfstests-dev/tests/generic/1230: line 247: kill: (1010272) -
No such process
Silence is golden
[root@jgarry-ol9new xfstests-dev]#
any idea (apart from _require_scratch_write_atomic_multi_fsblock)?
next prev parent reply other threads:[~2025-06-27 16:11 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
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 [this message]
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=b8bd60eb-c926-44f4-a0ff-b5de75803d85@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