All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH 1/1] fs/ubifs: increase logical eraseblock size
Date: Sat,  8 Jul 2023 18:36:44 +0200	[thread overview]
Message-ID: <20230708163644.710352-1-bernd@kuhls.net> (raw)

This value is unchanged since 2008 and too small for current images.

Fixes:
http://autobuild.buildroot.net/results/f72/f72918d63510b170e5da01bfa9c247cf9dcf507f/

Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
---
There is no particular reason for the new value, it was just the first
value I found working for this defconfig while increasing it in steps
of 0x10000.

 fs/ubifs/Config.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/ubifs/Config.in b/fs/ubifs/Config.in
index e79ab9a17e..bad26bf99f 100644
--- a/fs/ubifs/Config.in
+++ b/fs/ubifs/Config.in
@@ -7,7 +7,7 @@ if BR2_TARGET_ROOTFS_UBIFS
 
 config BR2_TARGET_ROOTFS_UBIFS_LEBSIZE
 	hex "logical eraseblock size"
-	default 0x1f800
+	default 0x3f800
 	help
 	  Logical eraseblock (LEB) size. The value provided here is
 	  passed to the -e/--leb-size option of mkfs.ubifs.
-- 
2.39.2

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2023-07-08 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-08 16:36 Bernd Kuhls [this message]
2023-07-10 17:26 ` [Buildroot] [PATCH 1/1] fs/ubifs: increase logical eraseblock size Thomas Petazzoni via buildroot
     [not found] <20230708163644.710352-1-bernd__8474.55057535029$1688834229$gmane$org@kuhls.net>
2023-07-09 12:39 ` Bernd Kuhls
2023-07-10 17:28   ` Thomas Petazzoni via buildroot

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=20230708163644.710352-1-bernd@kuhls.net \
    --to=bernd@kuhls.net \
    --cc=buildroot@buildroot.org \
    /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.