ltp.lists.linux.it archive mirror
 help / color / mirror / Atom feed
From: Li Wang <liwang@redhat.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: "Darrick J . Wong" <djwong@kernel.org>,
	linux-xfs@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	automated-testing@yoctoproject.org, LTP List <ltp@lists.linux.it>,
	automated-testing@lists.yoctoproject.org
Subject: Re: [LTP] [Automated-testing] [RFC PATCH 1/1] API: Allow to use xfs filesystems < 300 MB
Date: Sat, 20 Aug 2022 10:37:24 +0800	[thread overview]
Message-ID: <CAEemH2ehh1+WPtwjzere-JEHeBUpg27w4nZs6_QG71ZTAkUzpA@mail.gmail.com> (raw)
In-Reply-To: <Yv/kVXSK0xJGb3RO@pevik>


[-- Attachment #1.1: Type: text/plain, Size: 2262 bytes --]

Hi Petr, All,

On Sat, Aug 20, 2022 at 3:28 AM Petr Vorel <pvorel@suse.cz> wrote:

> Hi all,
>
> > Hi Cyril,
>
> > On Thu, Aug 18, 2022 at 1:28 PM Cyril Hrubis <chrubis@suse.cz> wrote:
> > > > > I'm starting to wonder if we should start tracking minimal FS size
> per
> > > > > filesystem since btrfs and xfs will likely to continue to grow and
> with
> > > > > that we will end up disabling the whole fs related testing on
> embedded
> > > > > boards with a little disk space. If we tracked that per filesystem
> we
> > > > > would be able to skip a subset of filesystems when there is not
> enough
> > > > > space. The downside is obviously that we would have to add a bit
> more
> > > > > complexity to the test library.
>
> > > > Maybe I could for start rewrite v2 (I've sent it without Cc kernel
> devs now it's
> > > > mainly LTP internal thing) as it just to have 300 MB for XFS and 256
> MB for the
> > > > rest. That would require to specify filesystem when acquiring device
> (NULL would
> > > > be for the default filesystem), that's would be worth if embedded
> folks counter
> > > > each MB. It'd be nice to hear from them.
>
> > > The 256MB limit was set previously due to btrfs, I bet that we can
> > > create smaller images for ext filesytems for example.
>
> Thanks for input, Geert!
>
> > Yeah, we used to have ext2 root file systems that fit on 1440 KiB
> floppies.
> These nice times when everything simple hadn't been solved yet ... :).
> > IIRC, ext3 does have a minimum size of 32 MiB or so.
> Interesting, I was able to create smaller.
>
> I did some testing minimal size (verified on chdir01 test):
> XFS: 300 MB, btrfs: 109 MB, ntfs: 2 MB, ext3: 2 MB, ext[24]: 1 MB, vfat: 1
> MB, exfat: 1 MB.
>
> I guess using XFS: 300 MB, btrfs: 109 MB and 16 MB for the rest could be
> enough.
>

I think so, tracking minimal FS size per FS is a practical idea.
But one thing we have to be aware of is that there may be different
minimal sizes for each FS version.
(so we'd better choose the maximum of minimal sizes).

16MB for general FS should be fine, I will help to test that if someone
works out the patch.



> But that would require to run all tests to see how many tests actually use
> bigger data.
>

Absolutely YES!

-- 
Regards,
Li Wang

[-- Attachment #1.2: Type: text/html, Size: 3699 bytes --]

[-- Attachment #2: Type: text/plain, Size: 60 bytes --]


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-08-20  2:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 20:40 [LTP] [RFC PATCH 1/1] API: Allow to use xfs filesystems < 300 MB Petr Vorel
2022-08-17 23:59 ` Darrick J. Wong
2022-08-18  5:08   ` Amir Goldstein
2022-08-18  9:45     ` Petr Vorel
2022-08-18  9:01   ` Petr Vorel
2022-08-18  9:53 ` Cyril Hrubis
2022-08-18 11:12   ` Petr Vorel
2022-08-18 11:30     ` Cyril Hrubis
2022-08-18 11:55       ` [LTP] [Automated-testing] " Geert Uytterhoeven
2022-08-19 19:28         ` Petr Vorel
2022-08-20  2:37           ` Li Wang [this message]
2022-08-22  9:36             ` Petr Vorel
2022-08-20  2:52   ` [LTP] " Li Wang
2022-08-24 10:21 ` Petr Vorel
2022-08-29  1:45   ` Li Wang
2024-04-03 14:24     ` Petr Vorel

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=CAEemH2ehh1+WPtwjzere-JEHeBUpg27w4nZs6_QG71ZTAkUzpA@mail.gmail.com \
    --to=liwang@redhat.com \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=automated-testing@yoctoproject.org \
    --cc=djwong@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    /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).