From: Thomas Gleixner <tglx@linutronix.de>
To: David Woodhouse <dwmw2@infradead.org>, Chris <csperandeo@intrinsyc.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Reliability of NAND JFFS2 vs YAFFS for Embedded Systems
Date: Sat, 14 Jun 2003 00:32:29 +0200 [thread overview]
Message-ID: <200306140032.29488.tglx@linutronix.de> (raw)
In-Reply-To: <1055484161.16455.133.camel@imladris.demon.co.uk>
On Friday 13 June 2003 08:02, David Woodhouse wrote:
> On Fri, 2003-06-13 at 01:05, Chris wrote:
> > I am considering moving to the YAFFS filesystem due to reliablity
> > concerns, but I am also wondering if YAFFS will have its own can of
> > worms. I would like to have reliability, performance and space but
> > reliability is the most important concern.
> >
> > Does anyone have experience with testing reliability of both
> > configurations?
> > If so what were the resutls?
>
> There's been powerfail testing done on JFFS2 on NOR; not yet for NAND
> and there are some known corner cases which need sorting out before I
> really undertake that.
I have done intensive powerfail testing on NAND. I have no problem with JFFS2
and YAFFS. I think both are reliable and have their (dis)advantages.
Both filesystems have invalid files on it, if the powerfail occures during a
file write. That's normal behaviour. This would be the same on your harddisk
or any other medium.
I have never seen a serious fs corruption neither on JFFS2 nor on YAFFS,
except for some development phases, when the code was buggy. That's normal
for work in progress too.
The only unsolved problem for JFFS2 on NAND at the moment is a writebuffer
flush failure. This has hit me once during a log term test, where a sector
went bad after > 1.200.000 erase cycles. But this did not corrupt the hole
filesystem. It was just the last written file, which was lost. It should be
not too hard to fix that at least, if somebody has enough time or someone
does a little sponsoring for that :)
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
prev parent reply other threads:[~2003-06-13 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 0:05 Reliability of NAND JFFS2 vs YAFFS for Embedded Systems Chris
2003-06-13 6:02 ` David Woodhouse
2003-06-13 22:32 ` Thomas Gleixner [this message]
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=200306140032.29488.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=csperandeo@intrinsyc.com \
--cc=dwmw2@infradead.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