From: Avinesh Kumar via ltp <ltp@lists.linux.it>
To: Wake Liu <wakel@google.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] inode01: Increase dev_min_size to prevent ENOSPC on exfat
Date: Mon, 24 Aug 2026 12:18:35 +0200 [thread overview]
Message-ID: <f9ff4fd3-5d0c-4fb1-8aba-65d5f266c600@suse.com> (raw)
In-Reply-To: <20260824085640.3514442-1-wakel@google.com>
Hi,
This issue is alreday being discussed in this PR:
https://github.com/linux-test-project/ltp/pull/1340
Thanks,
Avinesh
On 8/24/26 10:56 AM, Wake Liu wrote:
> The parallel scenario concurrently spawns multiple workers (default 5),
> each creating 2,185 files and directories, totaling 10,925 objects.
>
> On exfat, each file and directory occupies at least one cluster (default
> 32 KB for volumes > 256 MB), which requires ~350 MB of data clusters.
> With filesystem metadata (FAT, allocation bitmap, upcase table),
> directory growth, boundary alignment, and multi-worker concurrent
> allocation fragmentation, the current 512 MB device size is easily
> exhausted, leading to ENOSPC failures during write() or mkdir():
>
> inode01.c:61: TBROK: write(3,...) failed: ENOSPC (28)
> inode01.c:64: TBROK: mkdir(...) failed: ENOSPC (28)
>
> Increase dev_min_size to 1024 MB to provide sufficient headroom for the
> parallel scenario on exfat.
>
> Fixes: ecf418722780 ("inode01: increase dev_min_size to fit the peak usage in parallel scenario")
> Signed-off-by: Wake Liu <wakel@google.com>
> ---
> testcases/kernel/fs/inode/inode01.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/testcases/kernel/fs/inode/inode01.c b/testcases/kernel/fs/inode/inode01.c
> index d41ff2c62..87ee07612 100644
> --- a/testcases/kernel/fs/inode/inode01.c
> +++ b/testcases/kernel/fs/inode/inode01.c
> @@ -68,7 +68,7 @@ static void create_tree(const struct tcase *tc, const char *parent,
> }
>
> static void record_inode(struct inode_info *inodes, unsigned int idx,
> - const char *path, ino_t ino)
> + const char *path, uint64_t ino)
> {
> inodes[idx].ino = ino;
> snprintf(inodes[idx].path, sizeof(inodes[idx].path), "%s", path);
> @@ -256,7 +256,7 @@ static struct tst_test test = {
> .mount_device = 1,
> .all_filesystems = 1,
> .needs_root = 1,
> - .dev_min_size = 512,
> + .dev_min_size = 1024,
> .forks_child = 1,
> .needs_checkpoints = 1,
> .timeout = 300,
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-08-24 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 8:56 [LTP] [PATCH] inode01: Increase dev_min_size to prevent ENOSPC on exfat Wake Liu via ltp
2026-08-24 10:18 ` Avinesh Kumar via ltp [this message]
2026-08-25 7:38 ` Wake Liu via ltp
-- strict thread matches above, loose matches on Subject: below --
2026-08-28 11:41 Wake Liu via ltp
2026-08-31 8:45 ` Andrea Cervesato via ltp
2026-09-01 9:55 ` Wake Liu via ltp
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=f9ff4fd3-5d0c-4fb1-8aba-65d5f266c600@suse.com \
--to=ltp@lists.linux.it \
--cc=avinesh.kumar@suse.com \
--cc=wakel@google.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