From: Hamish Moffatt <hamish@cloud.net.au>
To: linux-mtd@lists.infradead.org
Subject: choosing a file system to use on NAND/UBI
Date: Fri, 28 Mar 2008 12:04:03 +1100 [thread overview]
Message-ID: <20080328010403.GB23610@cloud.net.au> (raw)
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.
I'm intending to use UBI for volume management and wear-levelling.
JFFS2 on UBI does not seem very fast, in particular mount time and
initial access (until cache is populated). I tried disabling compression
but that seemed to make it worse (mount time was doubled).
Will ubifs on UBI be better? Is it mature enough to use yet?
For static volumes you have UBI protecting you, so you should not need
file-system CRC checking as JFFS2 does, correct? Are there any file
systems which take advantage of this property?
Would I be better choosing LogFS or YAFFS1/2, perhaps without UBI?
thanks
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next reply other threads:[~2008-03-28 1:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 1:04 Hamish Moffatt [this message]
2008-03-28 6:33 ` choosing a file system to use on NAND/UBI Artem Bityutskiy
2008-04-07 5:12 ` Hamish Moffatt
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=20080328010403.GB23610@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.