public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>
To: zlang@redhat.com, fstests@vger.kernel.org
Cc: p.raghav@samsung.com, djwong@kernel.org, mcgrof@kernel.org,
	gost.dev@samsung.com, linux-xfs@vger.kernel.org
Subject: [PATCH 2/2] xfs/161: adapt the test case for LBS filesystem
Date: Mon, 22 Jan 2024 12:17:51 +0100	[thread overview]
Message-ID: <20240122111751.449762-3-kernel@pankajraghav.com> (raw)
In-Reply-To: <20240122111751.449762-1-kernel@pankajraghav.com>

From: Pankaj Raghav <p.raghav@samsung.com>

This test fails for >= 64k filesystem block size on a 4k PAGE_SIZE
system(see LBS efforts[1]). Adapt the blksz so that we create more than
one block for the testcase.

Cap the blksz to be at least 64k to retain the same behaviour as before
for smaller filesystem blocksizes.

[1] LBS effort: https://lore.kernel.org/lkml/20230915183848.1018717-1-kernel@pankajraghav.com/

Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>
---
 tests/xfs/161 | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/tests/xfs/161 b/tests/xfs/161
index 486fa6ca..f7b03f0e 100755
--- a/tests/xfs/161
+++ b/tests/xfs/161
@@ -38,9 +38,14 @@ _qmount_option "usrquota"
 _scratch_xfs_db -c 'version' -c 'sb 0' -c 'p' >> $seqres.full
 _scratch_mount >> $seqres.full
 
+min_blksz=65536
+file_blksz=$(_get_file_block_size "$SCRATCH_MNT")
+blksz=$(( 2 * $file_blksz))
+
+blksz=$(( blksz > min_blksz ? blksz : min_blksz ))
 # Force the block counters for uid 1 and 2 above zero
-_pwrite_byte 0x61 0 64k $SCRATCH_MNT/a >> $seqres.full
-_pwrite_byte 0x61 0 64k $SCRATCH_MNT/b >> $seqres.full
+_pwrite_byte 0x61 0 $blksz $SCRATCH_MNT/a >> $seqres.full
+_pwrite_byte 0x61 0 $blksz $SCRATCH_MNT/b >> $seqres.full
 sync
 chown 1 $SCRATCH_MNT/a
 chown 2 $SCRATCH_MNT/b
-- 
2.43.0


  parent reply	other threads:[~2024-01-22 11:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 11:17 [PATCH 0/2] fstest changes for LBS Pankaj Raghav (Samsung)
2024-01-22 11:17 ` [PATCH 1/2] xfs/558: scale blk IO size based on the filesystem blksz Pankaj Raghav (Samsung)
2024-01-22 16:53   ` Darrick J. Wong
2024-01-22 17:23     ` Pankaj Raghav
2024-03-13 20:08       ` Darrick J. Wong
2024-01-22 11:17 ` Pankaj Raghav (Samsung) [this message]
2024-01-22 16:57   ` [PATCH 2/2] xfs/161: adapt the test case for LBS filesystem Darrick J. Wong
2024-01-22 17:32     ` Pankaj Raghav
2024-01-25 16:06     ` Pankaj Raghav
2024-01-23  0:25 ` [PATCH 0/2] fstest changes for LBS Dave Chinner
2024-01-23  8:52   ` Pankaj Raghav
2024-01-23 13:43     ` Zorro Lang
2024-01-23 15:39       ` Ritesh Harjani
2024-01-23 16:33       ` Pankaj Raghav
2024-01-23 15:35     ` Ritesh Harjani
2024-01-23 16:40       ` Pankaj Raghav
2024-01-23 19:42         ` Ritesh Harjani
2024-01-23 20:21           ` Pankaj Raghav
2024-01-24 16:58             ` Darrick J. Wong
2024-01-24 21:06               ` Pankaj Raghav
  -- strict thread matches above, loose matches on Subject: below --
2024-10-16 23:15 [PATCHSET 1/2] fstests: fix fstests for 64k fsblock size Darrick J. Wong
2024-10-16 23:15 ` [PATCH 2/2] xfs/161: adapt the test case for LBS filesystem Darrick J. Wong
2024-10-22  5:48   ` Christoph Hellwig
2024-10-23  4:23   ` 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=20240122111751.449762-3-kernel@pankajraghav.com \
    --to=kernel@pankajraghav.com \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=gost.dev@samsung.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=p.raghav@samsung.com \
    --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