From: Pankaj Raghav <p.raghav@samsung.com>
To: "Darrick J. Wong" <djwong@kernel.org>,
Dave Chinner <david@fromorbit.com>
Cc: <zlang@redhat.com>, <fstests@vger.kernel.org>,
<mcgrof@kernel.org>, <gost.dev@samsung.com>,
<linux-xfs@vger.kernel.org>,
"Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>,
<chandan.babu@oracle.com>
Subject: Re: [PATCH 2/2] xfs/161: adapt the test case for LBS filesystem
Date: Thu, 25 Jan 2024 17:06:30 +0100 [thread overview]
Message-ID: <a05f3bfa-ee30-4309-b1e4-89f2cfb43510@samsung.com> (raw)
In-Reply-To: <20240122165756.GB6188@frogsfrogsfrogs>
On 22/01/2024 17:57, Darrick J. Wong wrote:
> On Mon, Jan 22, 2024 at 12:17:51PM +0100, Pankaj Raghav (Samsung) wrote:
>> 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.
>
> How does this fail, specifically? And, uh, what block sizes > 64k were
> tested?
>
> --D
>
>> 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/
>>
I tried the same test on a machine with 64k page size and block size, and I get the same error
and this patch fixes it!
Kernel version: 6.7.1
xfstest version: for-next
PAGE_SIZE: 64k
# Without this patch
ubuntu@xfstest:/mnt/linux/xfstests$ getconf PAGE_SIZE
65536
ubuntu@xfstest:/mnt/linux/xfstests$ sudo ./check -s 64k xfs/161
SECTION -- 64k
RECREATING -- xfs on /dev/sdb2
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/aarch64 xfstest 6.7.1-64k #8 SMP Thu Jan 25 13:38:41 UTC 2024
MKFS_OPTIONS -- -f -f -m reflink=1,rmapbt=1, -i sparse=1, -b size=64k, /dev/sdb3
MOUNT_OPTIONS -- /dev/sdb3 /mnt/scratch
xfs/161 6s ... - output mismatch (see /mnt/linux/xfstests/results/xfstest/6.7.1-64k/64k/xfs/161.out.bad)
--- tests/xfs/161.out 2024-01-25 15:36:48.869401419 +0000
+++ /mnt/linux/xfstests/results/xfstest/6.7.1-64k/64k/xfs/161.out.bad 2024-01-25
15:59:47.702340351 +0000
@@ -1,6 +1,15 @@
QA output created by 161
+Expected timer expiry (0) to be after now (1706198386).
Running xfs_repair to upgrade filesystem.
Adding large timestamp support to filesystem.
FEATURES: BIGTIME:YES
-grace2 expiry is in range
-grace2 expiry after remount is in range
...
(Run 'diff -u /mnt/linux/xfstests/tests/xfs/161.out
/mnt/linux/xfstests/results/xfstest/6.7.1-64k/64k/xfs/161.out.bad' to see the entire diff)
Ran: xfs/161
Failures: xfs/161
Failed 1 of 1 tests
SECTION -- 64k
=========================
Ran: xfs/161
Failures: xfs/161
Failed 1 of 1 tests
# With this patch:
ubuntu@xfstest:/mnt/linux/xfstests$ sudo ./check -s 64k xfs/161
SECTION -- 64k
RECREATING -- xfs on /dev/sdb2
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/aarch64 xfstest 6.7.1-64k #8 SMP Thu Jan 25 13:38:41 UTC 2024
MKFS_OPTIONS -- -f -f -m reflink=1,rmapbt=1, -i sparse=1, -b size=64k, /dev/sdb3
MOUNT_OPTIONS -- /dev/sdb3 /mnt/scratch
xfs/161 6s ... 6s
Ran: xfs/161
Passed all 1 tests
SECTION -- 64k
=========================
Ran: xfs/161
Passed all 1 tests
>> 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
>>
>>
next prev parent reply other threads:[~2024-01-25 16:06 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 ` [PATCH 2/2] xfs/161: adapt the test case for LBS filesystem Pankaj Raghav (Samsung)
2024-01-22 16:57 ` Darrick J. Wong
2024-01-22 17:32 ` Pankaj Raghav
2024-01-25 16:06 ` Pankaj Raghav [this message]
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=a05f3bfa-ee30-4309-b1e4-89f2cfb43510@samsung.com \
--to=p.raghav@samsung.com \
--cc=chandan.babu@oracle.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=gost.dev@samsung.com \
--cc=kernel@pankajraghav.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--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