From: Hamish Moffatt <hamish@cloud.net.au>
To: linux-mtd@lists.infradead.org
Subject: Re: choosing a file system to use on NAND/UBI
Date: Mon, 7 Apr 2008 15:12:59 +1000 [thread overview]
Message-ID: <20080407051259.GA3584@cloud.net.au> (raw)
In-Reply-To: <1206686024.3856.57.camel@sauron>
On Fri, Mar 28, 2008 at 08:33:44AM +0200, Artem Bityutskiy wrote:
> On Fri, 2008-03-28 at 12:04 +1100, Hamish Moffatt wrote:
> > I'm developing an embedded product which will have its root file system
> > on NAND. The root will be pre-prepared and installed using
> > flashcp/nandwrite/ubiupdatevol, and usually mounted read-only.
> > Occasionally we might want to mount it read/write for debug purposes.
> Please, tell the size of your flash and whether it SLC or MLC.
Just to finish this old discussion, it's a 512Mb SLC part. ie not very
big. I have tried UBIFS and I am very pleased with it. Performance is
much better than JFFS2, which was slow to mount and slow during early
reads (even when the image was processed with sumtool).
> > Will ubifs on UBI be better? Is it mature enough to use yet?
> UBIFS mounts very quickly. It is very stable. We find minor issues from
> time to time, but they are fixed quickly.
I noticed that the on-chip format just changed (nanoseconds etc). Do you
plan any more incompatible changes? This is the sort of maturity issue I
was worried about.
> > Would I be better choosing LogFS or YAFFS1/2, perhaps without UBI?
>
> Never used YAFFSx, but it might be worth trying and evaluating. Vs.
> LogFS - last time we tried it - it was too slow. It also did not
> implement wear-levelling and bad block handling.
>
> If you try to evaluate them - I would be interested to know about your
> experience.
I could not get a pre-generated YAFFS2 image to mount successfully, and
a call for assistance on the YAFFS mailing list went unanswered.
Although I'm interested in LogFS I don't have enough time to try it
thoroughly.
thanks,
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2008-04-07 5:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 1:04 choosing a file system to use on NAND/UBI Hamish Moffatt
2008-03-28 6:33 ` Artem Bityutskiy
2008-04-07 5:12 ` Hamish Moffatt [this message]
2008-04-07 7:13 ` Artem Bityutskiy
2008-04-07 7:32 ` Hamish Moffatt
2008-04-07 7:48 ` Hamish Moffatt
2008-04-07 7:56 ` Artem Bityutskiy
2008-04-07 11:20 ` Hamish Moffatt
2008-04-07 12:15 ` Artem Bityutskiy
2008-04-07 12:16 ` Artem Bityutskiy
2008-04-07 12:22 ` Hamish Moffatt
2008-04-07 12:44 ` Artem Bityutskiy
2008-04-07 15:31 ` Jamie Lokier
2008-04-08 10:21 ` Hamish Moffatt
2008-04-07 8:41 ` Artem Bityutskiy
2008-04-08 7:07 ` Artem Bityutskiy
2008-03-28 7:22 ` Adrian Hunter
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=20080407051259.GA3584@cloud.net.au \
--to=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 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.