From: Petr Vorel <pvorel@suse.cz>
To: Andrei Gherzan <andrei.gherzan@canonical.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] fs_fill: Fix test when running on a 256 CPU+ machine
Date: Wed, 8 Mar 2023 17:55:45 +0100 [thread overview]
Message-ID: <20230308165545.GA428998@pevik> (raw)
In-Reply-To: <Y/N53BN2yr7WEIzr@qwirkle>
Hi Andrei,
> > > The fs_fill test runs a fill test on all the supported filesystems. One
> > > of them being vfat. This filesystem is configured dynamically or through
> > > flags/arguments for its file allocation table type (12/16/32).
> > > The size of the test device (which is a loop-mounted fs) is 300MB. When not
> > > instructed, mkfs will "automatically select between 12, 16 and 32 bit,
> > > whatever fits better for the filesystem size"[1]. In the case of a 300Mb that
> > > would end up as FAT16.
> > Interesting. BTW we plan to change 300 MB to minimal filesystem which would fit
> > to all existing tests (255 MB was for Btrfs, 300 MB was for XFS, but there might
> > be minimal systems which can use vfat, ext4, ... with smaller resources, e.g.
> > 16 MB for filesystem). Therefore I wonder what is minimal reasonable required
> > size for vfat. i.e. what MB is required for FAT32? (I guess we don't want to
> > check FAT12 or FAT16).
> The minimum/maximum values depend on the sector size. I'm not sure about
> F12 but for the other ones I think it was 32MB for 512b sectors.
Thanks a lot for info. BTW I'm not convinced any more that using as smallest
loop device size as possible is a good idea.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-03-08 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 11:47 [LTP] [PATCH] fs_fill: Fix test when running on a 256 CPU+ machine Andrei Gherzan
2023-02-17 15:27 ` Petr Vorel
2023-02-20 13:47 ` Andrei Gherzan
2023-03-08 16:55 ` Petr Vorel [this message]
2023-03-09 16:24 ` Andrei Gherzan
2023-03-20 7:51 ` Petr Vorel
2023-03-20 16:04 ` Andrei Gherzan
2023-03-07 12:43 ` Richard Palethorpe
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=20230308165545.GA428998@pevik \
--to=pvorel@suse.cz \
--cc=andrei.gherzan@canonical.com \
--cc=ltp@lists.linux.it \
/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