public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Andrei Gherzan <andrei.gherzan@canonical.com>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] LTP fs_fill test on vfat - ENOSPC
Date: Thu, 16 Feb 2023 10:31:45 +0000	[thread overview]
Message-ID: <Y+4GEbRopmw5QA5r@qwirkle> (raw)
In-Reply-To: <Y+38qMc2Kdh2DPA7@yuki>

Hi. Thanks for your feedback.

On 23/02/16 10:51AM, Cyril Hrubis wrote:
> Hi!
> > There a couple of ways to deal with this:
> > 
> > 1. Force the filesystem creation in FAT32. This would be the best way
> > forward in my opinion, but I can't see anything that supports doing so on
> > a per-filesystem basis in LTP.
> > 2. Increase the minimal numbers of entries available in the root
> > directory via "-r ROOT-DIR-ENTRIES"[1]. This would only push the crash
> > on fewer systems.
> > 3. Use a subdirectory in the test setup. Something like /subdir/threadX.
> > If I'm not missing any support to do 1, this would probably be the
> > easiest to do.
> > 
> > I'm happy to go forward with a PR to fix this properly but looking
> > forward to your feedback on how to steer this.
> 
> For number 1 we could probably add a special case in the test library,
> something as (beware untested):
> 
> diff --git a/lib/tst_mkfs.c b/lib/tst_mkfs.c
> index 736324f04..0e6e9ebd1 100644
> --- a/lib/tst_mkfs.c
> +++ b/lib/tst_mkfs.c
> @@ -50,6 +50,9 @@ void tst_mkfs_(const char *file, const int lineno, void (cleanup_fn)(void),
>                 return;
>         }
> 
> +       if (!strcmp(fs_type, "vfat"))
> +               argv[pos++] = "-F 32";
> +
>         snprintf(mkfs, sizeof(mkfs), "mkfs.%s", fs_type);
> 
>         if (fs_opts) {

I did consider this as well, but I haven't proposed it initially because
I didn't want to come with a solution that will switch all tests to
Fat32. This is a limitation for tests that create a large enough number
of directories in the root of the filesystem, so I wanted to keep the
scope there.

I have tested, and we will locally go with my proposed 3rd option for
now. Does that sound resonable for a push to upstrem too? 

-- 
Andrei Gherzan

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

  reply	other threads:[~2023-02-16 10:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15 13:22 [LTP] LTP fs_fill test on vfat - ENOSPC Andrei Gherzan
2023-02-16  9:51 ` Cyril Hrubis
2023-02-16 10:31   ` Andrei Gherzan [this message]
2023-02-16 10:49     ` Cyril Hrubis
2023-02-16 11:09       ` Andrei Gherzan
2023-02-16 11:44         ` Cyril Hrubis
2023-02-16 11:50           ` Andrei Gherzan

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=Y+4GEbRopmw5QA5r@qwirkle \
    --to=andrei.gherzan@canonical.com \
    --cc=chrubis@suse.cz \
    --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