public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: "Adam S. Turowski" <a.turowski@wb.com.pl>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Adrian Hunter <ext-adrian.hunter@nokia.com>
Subject: Re: [UBIFS] Filesystem capacity
Date: Tue, 17 Feb 2009 08:11:51 +0200	[thread overview]
Message-ID: <1234851111.17790.218.camel@localhost.localdomain> (raw)
In-Reply-To: <20090217003921.GB20713@shareable.org>

On Tue, 2009-02-17 at 00:39 +0000, Jamie Lokier wrote:
> > 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.

I do not see any major flaw.

> What does "UBIFS does not fit data into the ends of eraseblocks the
> way JFFS2 does" mean?

JFFS2 can split nodes on 2 parts and put 1 part to the end of one
eraseblock, and the second part to the beginning of another eraseblocks.
UBIFS does not split data blocks. This is the difference.

However, UBIFS tries to write small data nodes to the ends of
eraseblocks to minimize the wastage. And I am not sure JFFS2 is doing
better job, but I did not deliberately compared them.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2009-02-17  6:12 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
2009-02-17  6:11     ` Artem Bityutskiy [this message]
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=1234851111.17790.218.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=a.turowski@wb.com.pl \
    --cc=ext-adrian.hunter@nokia.com \
    --cc=jamie@shareable.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