From: Hamish Moffatt <hamish@cloud.net.au>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mkfs.ubifs: support --squash-uids
Date: Thu, 8 May 2008 10:16:29 +1000 [thread overview]
Message-ID: <20080508001628.GA5014@cloud.net.au> (raw)
In-Reply-To: <1210069392.3645.34.camel@sauron>
On Tue, May 06, 2008 at 01:23:12PM +0300, Artem Bityutskiy wrote:
> Fundamentally, mkfs.ubifs has to know FS size because UBIFS maintains
> and stores per-LEB information (like amount of dirty and free space in
> each LEB) in so-called LPT area on the media. So obviously, the size of
> this area depends on the total amount of LEBs, i.e. on the volume size.
OK (and thanks for adding this information to the web site also.)
In my case I am preparing images with mkfs.ubifs, and mounting them
read-only on my embedded target. In that case, could the max LEB count
be calculated automatically to fit the files and the LPT area?
I added support for ubifs images into buildroot. The user must configure
their LEB size, max I/O size, and max LEB count as these are all
required for mkfs.ubifs. Is there a formula to calculate an approximate
max LEB count from the volume size and LEB size? I will need to improve
the documentation for these parameters shown to the buildroot users
(although probably I'm the only one using the ubifs target so far!).
thanks
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2008-05-08 0:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 5:16 [PATCH] mkfs.ubifs: support --squash-uids Hamish Moffatt
2008-05-05 7:31 ` Artem Bityutskiy
2008-05-05 8:46 ` Hamish Moffatt
2008-05-05 8:52 ` Artem Bityutskiy
2008-05-06 11:00 ` Artem Bityutskiy
2008-05-06 6:38 ` Artem Bityutskiy
2008-05-06 9:46 ` Hamish Moffatt
2008-05-06 10:23 ` Artem Bityutskiy
2008-05-08 0:16 ` Hamish Moffatt [this message]
2008-05-08 6:34 ` Artem Bityutskiy
2008-05-07 12:55 ` Artem Bityutskiy
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=20080508001628.GA5014@cloud.net.au \
--to=hamish@cloud.net.au \
--cc=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox