From: Cyril Hrubis <chrubis@suse.cz>
To: Andrei Gherzan <andrei.gherzan@canonical.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] LTP fs_fill test on vfat - ENOSPC
Date: Thu, 16 Feb 2023 11:49:11 +0100 [thread overview]
Message-ID: <Y+4KJ3tgxRiIr7JN@yuki> (raw)
In-Reply-To: <Y+4GEbRopmw5QA5r@qwirkle>
Hi!
> 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?
Sure, this sounds reasonable as well.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-02-16 10:48 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
2023-02-16 10:49 ` Cyril Hrubis [this message]
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+4KJ3tgxRiIr7JN@yuki \
--to=chrubis@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