public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Cc: fstests@vger.kernel.org, Ritesh Harjani <ritesh.list@gmail.com>,
	john.g.garry@oracle.com
Subject: Re: [RFC 05/12] generic/769: Add atomic write test using fio verify on file mixed mappings
Date: Wed, 11 Jun 2025 08:35:38 -0700	[thread overview]
Message-ID: <20250611153538.GL6143@frogsfrogsfrogs> (raw)
In-Reply-To: <15c49ab581996987e060ee44cda4c58c4ceac1f8.1749629233.git.ojaswin@linux.ibm.com>

On Wed, Jun 11, 2025 at 03:04:48PM +0530, Ojaswin Mujoo wrote:
> From: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
> 
> This tests uses fio to first create a file with mixed mappings. Then it
> does atomic writes using aio dio with parallel jobs to the same file
> with mixed mappings. This forces the filesystem allocator to allocate
> extents over mixed mapping regions to stress FS block allocators.
> 
> Signed-off-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
> Signed-off-by: Ojaswin Mujoo <ojaswin@linux.ibm.com>
> ---
>  tests/generic/769     | 101 ++++++++++++++++++++++++++++++++++++++++++
>  tests/generic/769.out |   2 +
>  2 files changed, 103 insertions(+)
>  create mode 100755 tests/generic/769
>  create mode 100644 tests/generic/769.out
> 
> diff --git a/tests/generic/769 b/tests/generic/769
> new file mode 100755
> index 00000000..469d6344
> --- /dev/null
> +++ b/tests/generic/769
> @@ -0,0 +1,101 @@
> +#! /bin/bash
> +# SPDX-License-Identifier: GPL-2.0
> +# Copyright (c) 2025 IBM Corporation. All Rights Reserved.
> +#
> +# FS QA Test 769
> +#
> +# Validate FS atomic write using fio crc check verifier on mixed mappings
> +# of a file.
> +#
> +. ./common/preamble
> +. ./common/atomicwrites
> +
> +_begin_fstest auto aio rw atomicwrites
> +
> +_require_scratch_write_atomic_multi_fsblock
> +_require_odirect
> +_require_aio
> +
> +function max()
> +{
> +	if (( $1 > $2 )); then
> +		echo "$1"
> +	else
> +		echo "$2"
> +	fi
> +}

Yeah, there's that function again.

The rest of the test looks fine.

--D

> +
> +_scratch_mkfs >> $seqres.full 2>&1
> +_scratch_mount
> +
> +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")
> +aw_bsize=$(max "$awu_min_write" "$((awu_max_write/4))")
> +
> +fsbsize=$(_get_block_size $SCRATCH_MNT)
> +
> +fio_config=$tmp.fio
> +fio_out=$tmp.fio.out
> +
> +FIO_LOAD=$(($(nproc) * 2 * LOAD_FACTOR))
> +SIZE=$((128 * 1024 * 1024))
> +
> +cat >$fio_config <<EOF
> +[global]
> +ioengine=libaio
> +fallocate=none
> +filename=$SCRATCH_MNT/test-file
> +filesize=$SIZE
> +bs=$fsbsize
> +direct=1
> +verify=0
> +group_reporting=1
> +
> +# Create written extents
> +[written_blocks]
> +stonewall
> +ioengine=libaio
> +rw=randwrite
> +io_size=$((SIZE/3))
> +random_generator=lfsr
> +
> +# Create unwritten extents
> +[unwritten_blocks]
> +stonewall
> +ioengine=falloc
> +rw=randwrite
> +io_size=$((SIZE/3))
> +random_generator=lfsr
> +
> +# atomic write to mixed mappings of written/unwritten/holes
> +[atomic_write_aio_dio_job]
> +stonewall
> +direct=1
> +ioengine=libaio
> +rw=randwrite
> +bs=$aw_bsize
> +iodepth=$FIO_LOAD
> +numjobs=$FIO_LOAD
> +size=$SIZE
> +random_generator=lfsr
> +verify_state_save=0
> +verify=crc32c
> +verify_fatal=1
> +verify_dump=0
> +verify_backlog=1024
> +verify_async=4
> +verify_write_sequence=0
> +atomic=1
> +EOF
> +
> +_require_fio $fio_config
> +
> +cat $fio_config >> $seqres.full
> +$FIO_PROG $fio_config --output=$fio_out
> +cat $fio_out >> $seqres.full
> +
> +# success, all done
> +echo Silence is golden
> +status=0
> +exit
> diff --git a/tests/generic/769.out b/tests/generic/769.out
> new file mode 100644
> index 00000000..1512b439
> --- /dev/null
> +++ b/tests/generic/769.out
> @@ -0,0 +1,2 @@
> +QA output created by 769
> +Silence is golden
> -- 
> 2.49.0
> 
> 

  reply	other threads:[~2025-06-11 15:35 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11  9:34 [RFC 00/12] Add more tests for multi fs block atomic writes Ojaswin Mujoo
2025-06-11  9:34 ` [RFC 01/12] common/preamble: Fix fsx for ext4 with bigalloc Ojaswin Mujoo
2025-06-11 14:30   ` Darrick J. Wong
2025-06-12  6:11     ` Ojaswin Mujoo
2025-06-12 14:36       ` Darrick J. Wong
2025-06-13  5:31         ` Ojaswin Mujoo
2025-06-13 15:04           ` Darrick J. Wong
2025-06-17  6:22             ` Ojaswin Mujoo
2025-06-30 15:27               ` Darrick J. Wong
2025-06-18 19:13   ` Zorro Lang
2025-06-20  6:21     ` Ojaswin Mujoo
2025-06-20  9:59       ` Zorro Lang
2025-06-11  9:34 ` [RFC 02/12] common/rc: Add a helper to run fsx on a given file Ojaswin Mujoo
2025-06-11 14:31   ` Darrick J. Wong
2025-06-12  6:17     ` Ojaswin Mujoo
2025-06-12 14:35       ` Darrick J. Wong
2025-06-11  9:34 ` [RFC 03/12] ltp/fsx.c: Add atomic writes support to fsx Ojaswin Mujoo
2025-06-11 14:35   ` Darrick J. Wong
2025-06-12  6:18     ` Ojaswin Mujoo
2025-06-11  9:34 ` [RFC 04/12] generic/767: Add atomic write test using fio crc check verifier Ojaswin Mujoo
2025-06-11 14:42   ` Darrick J. Wong
2025-06-12  6:22     ` Ojaswin Mujoo
2025-06-12 14:55       ` Darrick J. Wong
2025-06-18 19:34   ` Zorro Lang
2025-06-20  7:06     ` Ojaswin Mujoo
2025-06-11  9:34 ` [RFC 05/12] generic/769: Add atomic write test using fio verify on file mixed mappings Ojaswin Mujoo
2025-06-11 15:35   ` Darrick J. Wong [this message]
2025-06-11  9:34 ` [RFC 06/12] generic/770: Add atomic write multi-fsblock O_[D]SYNC tests Ojaswin Mujoo
2025-06-11 15:36   ` Darrick J. Wong
2025-06-12  6:23     ` Ojaswin Mujoo
2025-06-18 20:17   ` Zorro Lang
2025-06-20  8:20     ` Ojaswin Mujoo
2025-06-20 12:12       ` Zorro Lang
2025-06-11  9:34 ` [RFC 07/12] generic/771: Stress fsx with atomic writes enabled Ojaswin Mujoo
2025-06-11 14:45   ` Darrick J. Wong
2025-06-12  6:27     ` Ojaswin Mujoo
2025-06-12 15:14       ` Darrick J. Wong
2025-06-13  5:20         ` Ojaswin Mujoo
2025-06-18 20:27   ` Zorro Lang
2025-06-20  8:26     ` Ojaswin Mujoo
2025-06-11  9:34 ` [RFC 08/12] generic/772: Add sudden shutdown tests for multi block atomic writes Ojaswin Mujoo
2025-06-11 15:38   ` Darrick J. Wong
2025-06-12  6:28     ` Ojaswin Mujoo
2025-06-19  7:15   ` Zorro Lang
2025-06-20 11:11     ` Ojaswin Mujoo
2025-06-20 14:05   ` John Garry
2025-06-20 15:24     ` Ojaswin Mujoo
2025-06-11  9:34 ` [RFC 09/12] ext4/061: Atomic writes stress test for bigalloc using fio crc verifier Ojaswin Mujoo
2025-06-19  7:43   ` Zorro Lang
2025-06-20 15:08     ` Ojaswin Mujoo
2025-06-20 16:53       ` Zorro Lang
2025-06-11  9:34 ` [RFC 10/12] ext4/062: Atomic writes test for bigalloc using fio crc verifier on multiple files Ojaswin Mujoo
2025-06-12 10:26   ` John Garry
2025-06-13  5:37     ` Ojaswin Mujoo
2025-06-20 14:01       ` John Garry
2025-06-20 16:49         ` Ojaswin Mujoo
2025-06-19  7:45   ` Zorro Lang
2025-06-11  9:34 ` [RFC 11/12] ext4/063: Atomic write test for extent split across leaf nodes Ojaswin Mujoo
2025-06-19  7:52   ` Zorro Lang
2025-06-11  9:34 ` [RFC 12/12] ext4/064: Add atomic write tests for journal credit calculation Ojaswin Mujoo
2025-06-19  7:58   ` Zorro Lang

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=20250611153538.GL6143@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=john.g.garry@oracle.com \
    --cc=ojaswin@linux.ibm.com \
    --cc=ritesh.list@gmail.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