All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wake Liu via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Cc: Wake Liu <wakel@google.com>
Subject: [LTP] [PATCH] inode01: Drop redundant 512MB dev_min_size requirement
Date: Tue, 17 Nov 2026 12:56:58 +0000	[thread overview]
Message-ID: <20261117125658.1743505-1-wakel@google.com> (raw)

Commit ecf418722780 ("inode01: increase dev_min_size to fit the peak
usage in parallel scenario") raised dev_min_size from the default 300MB
to 512MB because mkfs.exfat defaulted to a 32KB cluster size on volumes
larger than 256MB, providing only ~9,600 clusters on a 300MB device for
the ~10,925 objects created across the 5 parallel workers.

Subsequently, commit 4bf4da8c6fda ("inode01: Configure 4KB cluster size
on exfat to prevent ENOSPC") explicitly configured mkfs.exfat with a 4KB
cluster size (-c 4K). With 4KB clusters, the 10,925 objects consume
under 50MB at peak, and the default 300MB loop device provides ~76,800
clusters on exfat, which is more than sufficient for all supported
filesystems.

Drop the redundant .dev_min_size = 512 setting so inode01 uses the
default 300MB device size and avoids unnecessary ENOSPC failures when
allocating the loop backing file on storage-constrained systems.

Signed-off-by: Wake Liu <wakel@google.com>
---
 testcases/kernel/fs/inode/inode01.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/testcases/kernel/fs/inode/inode01.c b/testcases/kernel/fs/inode/inode01.c
index e7190fc99..09e0e9da0 100644
--- a/testcases/kernel/fs/inode/inode01.c
+++ b/testcases/kernel/fs/inode/inode01.c
@@ -260,7 +260,6 @@ static struct tst_test test = {
 		{}
 	},
 	.needs_root = 1,
-	.dev_min_size = 512,
 	.forks_child = 1,
 	.needs_checkpoints = 1,
 	.timeout = 300,
-- 
2.56.0.679.gc527c65306-goog


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

                 reply	other threads:[~2026-11-17 12:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261117125658.1743505-1-wakel@google.com \
    --to=ltp@lists.linux.it \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.