From: Murphy Zhou <jencce.kernel@gmail.com>
To: Zorro Lang <zlang@redhat.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
fstests <fstests@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] tests: increase fs size for mkfs
Date: Wed, 31 Aug 2022 09:53:55 +0800 [thread overview]
Message-ID: <CADJHv_v1sJSythY2RDA6tYBtuY7O_0zgKLxXhAPw7zpvMunXvA@mail.gmail.com> (raw)
In-Reply-To: <CADJHv_tFtH_fihVFGLUB=GyjGJ+Neo-pj8S5DGJDFOHrW12EOA@mail.gmail.com>
Oops.. Darrick left a workaround in the xfsprogs code for fstests. My
test setup missed TEST_DEV export somehow and the workaround was not
working.
Nevermind for this patchset.. My bloody hours...
On Wed, Aug 31, 2022 at 8:18 AM Murphy Zhou <jencce.kernel@gmail.com> wrote:
>
> On Wed, Aug 31, 2022 at 3:07 AM Zorro Lang <zlang@redhat.com> wrote:
> >
> > On Tue, Aug 30, 2022 at 07:46:40AM -0700, Darrick J. Wong wrote:
> > > On Tue, Aug 30, 2022 at 03:36:34PM +0800, Zorro Lang wrote:
> > > > On Tue, Aug 30, 2022 at 12:44:30PM +0800, Murphy Zhou wrote:
> > > > > Since this xfsprogs commit:
> > > > > 6e0ed3d19c54 mkfs: stop allowing tiny filesystems
> > > > > XFS requires filesystem size bigger then 300m.
> > > >
> > > > I'm wondering if we can just use 300M, or 512M is better. CC linux-xfs to
> > > > get more discussion about how to deal with this change on mkfs.xfs.
> > > >
> > > > >
> > > > > Increase thoese numbers to 512M at least. There is no special
> > > > > reason for the magic number 512, just double it from original
> > > > > 256M and being reasonable small.
> > > >
> > > > Hmm... do we need a global parameter to define the minimal XFS size,
> > > > or even minimal local fs size? e.g. MIN_XFS_SIZE, or MIN_FS_SIZE ...
> > >
> > > I think it would be a convenient time to create a helper to capture
> > > that, seeing as the LTP developers recently let slip that they have such
> > > a thing somewhere, and min fs size logic is scattered around fstests.
> >
> > It's a little hard to find out all cases which use the minimal fs size.
> > But for xfs, I think we can do that with this chance. We can have:
> >
> > export XFS_MIN_SIZE=$((300 * 1024 * 1024))
> > export XFS_MIN_LOG_SIZE=$((64 * 1024 * 1024))
> >
> > at first, then init minimal $FSTYP size likes:
> >
> > init_min_fs_size()
> > {
> > case $FSTYP in
> > xfs)
> > FS_MIN_SIZE=$XFS_MIN_SIZE
> > ;;
> > *)
> > FS_MIN_SIZE="unlimited" # or a big enough size??
> > ;;
> > esac
> > }
> >
> > Then other fs can follow this to add their size limitation.
> > Any better ideas?
>
> In generic/042 f2fs has a similar kind of limitation.
>
> Let me check how LTP guys handle this.
>
> Thanks,
> Murphy
>
> >
> > Thanks,
> > Zorro
> >
> > >
> >
> snipped
> >
next prev parent reply other threads:[~2022-08-31 1:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 4:44 [PATCH v3 0/4] tweaks for denying tiny xfs Murphy Zhou
2022-08-30 4:44 ` [PATCH v3 1/4] tests: increase fs size for mkfs Murphy Zhou
2022-08-30 7:36 ` Zorro Lang
2022-08-30 14:46 ` Darrick J. Wong
2022-08-30 19:07 ` Zorro Lang
2022-08-31 0:18 ` Murphy Zhou
2022-08-31 1:53 ` Murphy Zhou [this message]
2022-08-31 5:04 ` Zorro Lang
2022-08-31 9:34 ` Murphy Zhou
2022-08-30 4:44 ` [PATCH v3 2/4] tests: increase xfs log size Murphy Zhou
2022-08-30 4:44 ` [PATCH v3 3/4] tests/xfs: remove single-AG options Murphy Zhou
2022-08-30 13:42 ` Zorro Lang
2022-08-31 0:02 ` Murphy Zhou
2022-08-30 15:05 ` Darrick J. Wong
2022-08-31 0:10 ` Murphy Zhou
2022-08-30 4:44 ` [PATCH v3 4/4] xfs/144: remove testing root dir inode in AG 1 Murphy Zhou
2022-08-30 7:49 ` Zorro Lang
2022-08-30 14:59 ` Darrick J. Wong
2022-08-30 23:45 ` Murphy Zhou
2022-08-30 23:42 ` Murphy Zhou
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=CADJHv_v1sJSythY2RDA6tYBtuY7O_0zgKLxXhAPw7zpvMunXvA@mail.gmail.com \
--to=jencce.kernel@gmail.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.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;
as well as URLs for NNTP newsgroup(s).