From: Richard Weinberger <richard@nod.at>
To: Mauri Sandberg <maukka@ext.kapsi.fi>
Cc: david oberhollenzer <david.oberhollenzer@sigma-star.at>,
linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] mkfs.ubifs: Add option to minimize the amount of LEBs
Date: Sat, 6 Jan 2024 11:16:01 +0100 (CET) [thread overview]
Message-ID: <1214686551.202632.1704536161145.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <fbce5a93-c3b8-45f4-9698-c76838ac5fea@ext.kapsi.fi>
----- Ursprüngliche Mail -----
> Von: "Mauri Sandberg" <maukka@ext.kapsi.fi>
>> Use case for the new option would be when you want to have a
>> non-mutable filesystem in a static ubifs volume and another
>> volume for writable data.
>>
>> Currently you can find the minimal LEB count by running the
>> mkfs.ubifs once with too small max_leb_cnt. This patch uses
>> the already calculated minimal amount of LEBs as the max_leb_cnt
>> and then proceeds to create the image as usual.
[...]
> Friendly ping. Also bringing in Richard and David as I thought at least
> they could be relevant maintainers. Thanks.
Seems like a legit feature. But what will happen if somebody tries to
use a minimized UBIFS in rw-mode?
I fear then UBIFS will fail because it has not enough log LEBs or such?
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2024-01-06 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 13:56 [PATCH] mkfs.ubifs: Add option to minimize the amount of LEBs Mauri Sandberg
2024-01-06 6:49 ` Mauri Sandberg
2024-01-06 10:16 ` Richard Weinberger [this message]
2024-01-06 14:46 ` Mauri Sandberg
2024-01-06 15:23 ` Richard Weinberger
2024-01-07 7:53 ` Mauri Sandberg
2024-01-07 12:54 ` Richard Weinberger
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=1214686551.202632.1704536161145.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=david.oberhollenzer@sigma-star.at \
--cc=linux-mtd@lists.infradead.org \
--cc=maukka@ext.kapsi.fi \
/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