From: Pankaj Raghav <p.raghav@samsung.com>
To: "Darrick J. Wong" <djwong@kernel.org>,
"Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>
Cc: <fstests@vger.kernel.org>, <zlang@redhat.com>,
Dave Chinner <david@fromorbit.com>, <mcgrof@kernel.org>,
<gost.dev@samsung.com>, <linux-xfs@vger.kernel.org>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Subject: Re: fstest failure due to filesystem size for 16k, 32k and 64k FSB
Date: Fri, 2 Feb 2024 18:18:32 +0100 [thread overview]
Message-ID: <aa37283d-227f-48af-a639-43dc7113a483@samsung.com> (raw)
In-Reply-To: <20240202164644.GK616564@frogsfrogsfrogs>
>> I still see some errors in generic/081 and generic/108 that have been
>> modified in your patch with the same issue.
>>
>> This is the mkfs option I am using:
>> -m reflink=1,rmapbt=1, -i sparse=1, -b size=64k
>>
>> And with that:
>> $ ./check -s 64k generic/042 generic/081 generic/108 generic/704 generic/730 generic/731 xfs/279
>>
>> ...
>> generic/081.out.bad:
>> +max log size 1732 smaller than min log size 2028, filesystem is too small
>> ...
>> generic/108.out.bad:
>> +max log size 1876 smaller than min log size 2028, filesystem is too small
>> ...
>> SECTION -- 64k
>> =========================
>> Ran: generic/042 generic/081 generic/108 generic/704 generic/730 generic/731 xfs/279
>> Failures: generic/081 generic/108
>> Failed 2 of 7 tests
>>
>> **Increasing the size** to 600M fixes all the test in 64k system.
>
> Huh. Can you send me the mkfs output (or xfs_info after the fact) so I
> can compare your setup with mine? I'm curious about what's affecting
> the layout here -- maybe you have -s size=4k or something?
>
> (I don't want to stray too far from the /actual/ mkfs minimum fs size of
> 300M.)
>
I am using v6.8-rc2 with xfsprogs 6.5.0 and xfstests v2024.01.14 (with your patch on top)
Using oracle OCI instance with 64k page size support.
config:
[default]
FSTYP=xfs
RESULT_BASE=$PWD/results/$HOST/$(uname -r)
DUMP_CORRUPT_FS=1
CANON_DEVS=yes
RECREATE_TEST_DEV=true
TEST_DEV=/dev/sdb2
TEST_DIR=/mnt/test
SCRATCH_DEV=/dev/sdb3
SCRATCH_MNT=/mnt/scratch
LOGWRITES_DEV=/dev/sdb4
[64k]
MKFS_OPTIONS='-f -m reflink=1,rmapbt=1, -i sparse=1, -b size=64k,'
If I use 600MB and if the tests run, then this is the xfs_info I am getting on
the test device (test device should have the same config as scratch as I use RECREATE_TEST_DEV=true):
[nix-shell:/mnt/linux/xfstests]$ sudo xfs_info /dev/sdb2
meta-data=/dev/sdb2 isize=512 agcount=4, agsize=102400 blks
= sectsz=4096 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=1
= reflink=1 bigtime=1 inobtcount=1 nrext64=1
data = bsize=65536 blocks=409600, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=65536 ascii-ci=0, ftype=1
log =internal log bsize=65536 blocks=2613, version=2
= sectsz=4096 sunit=1 blks, lazy-count=1
realtime =none extsz=65536 blocks=0, rtextents=0
Let me know if you need more information.
--
Pankaj
prev parent reply other threads:[~2024-02-02 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240130131803eucas1p280d9355ca3f8dc94073aff54555e3820@eucas1p2.samsung.com>
2024-01-30 13:18 ` fstest failure due to filesystem size for 16k, 32k and 64k FSB Pankaj Raghav
2024-01-30 19:56 ` Darrick J. Wong
2024-01-30 20:34 ` Pankaj Raghav
2024-01-31 3:48 ` Darrick J. Wong
2024-01-31 14:05 ` Pankaj Raghav (Samsung)
2024-01-31 18:28 ` Darrick J. Wong
2024-02-01 15:44 ` Pankaj Raghav (Samsung)
2024-02-02 16:46 ` Darrick J. Wong
2024-02-02 17:18 ` Pankaj Raghav [this message]
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=aa37283d-227f-48af-a639-43dc7113a483@samsung.com \
--to=p.raghav@samsung.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=ritesh.list@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).