From: Jamie Lokier <jamie@shareable.org>
To: Adrian Hunter <ext-adrian.hunter@nokia.com>
Cc: "Adam S. Turowski" <a.turowski@wb.com.pl>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [UBIFS] Filesystem capacity
Date: Tue, 17 Feb 2009 00:39:22 +0000 [thread overview]
Message-ID: <20090217003921.GB20713@shareable.org> (raw)
In-Reply-To: <49998C2D.7000505@nokia.com>
Adrian Hunter wrote:
> Adam S. Turowski wrote:
> > jffs2:
> > nor: 28361 kB
> > nand: 31200 kB
> >
> > [ubifs]:
> > nor: 26960 kB (I can live with that)
> > nand: 23552 kB (With that I cannot)
>
> It is because the LEB size is relatively small, and UBIFS does not
> fit data into the ends of eraseblocks the way JFFS2 does. Your options
> are:
> 1. use JFFS2
> 2. amend your NAND driver to pretend that eraseblocks are bigger
> than they really are, by treating 2 (or 4 or 8 etc) as one eraseblock
> 3. create another MTD driver that sits on top of the NAND driver
> and does the same as 2
>
> The disadvantage of 2 or 3 is that it also multiples the effective number
> of bad blocks.
Is this a major flaw of UBIFS? I was thinking of using UBIFS for a
project but this makes me wonder if it's a good idea.
What does "UBIFS does not fit data into the ends of eraseblocks the
way JFFS2 does" mean?
Thanks,
-- Jamie
next prev parent reply other threads:[~2009-02-17 0:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 14:44 [UBIFS] Filesystem capacity Adam S. Turowski
2009-02-16 15:54 ` Adrian Hunter
2009-02-17 0:39 ` Jamie Lokier [this message]
2009-02-17 6:11 ` Artem Bityutskiy
2009-02-17 8:01 ` Artem Bityutskiy
2009-02-17 6:07 ` Artem Bityutskiy
2009-02-17 7:39 ` Adam S. Turowski
2009-02-17 7:57 ` Artem Bityutskiy
2009-02-17 9:16 ` Jamie Lokier
2009-02-17 9:31 ` 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=20090217003921.GB20713@shareable.org \
--to=jamie@shareable.org \
--cc=a.turowski@wb.com.pl \
--cc=ext-adrian.hunter@nokia.com \
--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 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.