From: Artem Bityutskiy <dedekind@infradead.org>
To: Hamish Moffatt <hamish@cloud.net.au>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mkfs.ubifs: support --squash-uids
Date: Tue, 06 May 2008 13:23:12 +0300 [thread overview]
Message-ID: <1210069392.3645.34.camel@sauron> (raw)
In-Reply-To: <20080506094642.GB23685@cloud.net.au>
On Tue, 2008-05-06 at 19:46 +1000, Hamish Moffatt wrote:
> Yes it was against the v0.4 tag.
>
> mkfs.jffs2 and genext2fs both use -P as the short version of
> --squash-perms, so mkfs.ubifs will have to use something different. No
> big deal however (although they are pretty similar otherwise).
Hmm, ok, then I will make it -p back. I just wanted to reserve -p for
other purposes, but this is not important anymore. I'v pushed
corresponding patch.
> Also, what is the purpose of --max-leb-cnt? It seems to be just a safety
> check that the volume will fit? It's a bit unusual.
It is a form of specifying FS size. But instead of specifying exact FS
size, you specify maximum FS size. This means that it will be possible
to put the image on smaller volumes as well, which is quite handy
because due to random amount of initial NAND bad blocks different
instances of the same device may have a bit different volume sizes.
E.g., rootfs partition may be 500MiB or 501MiB on a 512MiB NAND,
depending on how many initial bad block NAND contains.
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.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-05-06 10:24 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 [this message]
2008-05-08 0:16 ` Hamish Moffatt
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=1210069392.3645.34.camel@sauron \
--to=dedekind@infradead.org \
--cc=hamish@cloud.net.au \
--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