All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: "Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>
Cc: Pankaj Raghav <p.raghav@samsung.com>,
	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 08:46:44 -0800	[thread overview]
Message-ID: <20240202164644.GK616564@frogsfrogsfrogs> (raw)
In-Reply-To: <f5wwi5oqok5p6somhubriesmmhlvvid7csszy5cmjqem37jy4g@2of2bw4azlvx>

On Thu, Feb 01, 2024 at 04:44:36PM +0100, Pankaj Raghav (Samsung) wrote:
> On Wed, Jan 31, 2024 at 10:28:58AM -0800, Darrick J. Wong wrote:
> > On Wed, Jan 31, 2024 at 03:05:48PM +0100, Pankaj Raghav (Samsung) wrote:
> > > > > 
> > > > > Thanks for the reply. So we can have a small `if` conditional block for xfs
> > > > > to have fs size = 500M in generic test cases.
> > > > 
> > > > I'd suggest creating a helper where you pass in the fs size you want and
> > > > it rounds that up to the minimum value.  That would then get passed to
> > > > _scratch_mkfs_sized or _scsi_debug_get_dev.
> > > > 
> > > > (testing this as we speak...)
> > > 
> > > I would be more than happy if you send a patch for
> > > this but I also know you are pretty busy, so let me know if you want me
> > > to send a patch for this issue.
> > > 
> > > You had something like this in mind?
> > 
> > Close, but something more like below.  It's not exhaustive; it merely
> > makes the xfs 64k bs tests pass:
> > 
> 
> 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.)

--D

> 
> The patch itself including `_small_fs_size_mb()` looks good to me.
> 
> > From: Darrick J. Wong <djwong@kernel.org>
> > Subject: [PATCH] misc: fix test that fail formatting with 64k blocksize
> > 
> > There's a bunch of tests that fail the formatting step when the test run
> > is configured to use XFS with a 64k blocksize.  This happens because XFS
> > doesn't really support that combination due to minimum log size
> > constraints.  Fix the test to format larger devices in that case.
> > 
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > ---
> >  common/rc         |   29 +++++++++++++++++++++++++++++
> >  tests/generic/042 |    9 +--------
> >  tests/generic/081 |    7 +++++--
> >  tests/generic/108 |    6 ++++--
> >  tests/generic/704 |    3 ++-
> >  tests/generic/730 |    3 ++-
> >  tests/generic/731 |    3 ++-
> >  tests/xfs/279     |    7 ++++---
> 
> As I indicated at the start of the thread, we need to also fix:
> generic/455 generic/457 generic/482 shared/298
> 
> Thanks!
> --
> Pankaj Raghav
> 

  reply	other threads:[~2024-02-02 16:46 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 [this message]
2024-02-02 17:18                 ` Pankaj Raghav

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=20240202164644.GK616564@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=david@fromorbit.com \
    --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=p.raghav@samsung.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.