From: Jamie Lokier <jamie@shareable.org>
To: Charles Manning <manningc2@actrix.gen.nz>
Cc: linux-mtd@lists.infradead.org,
"Wolfgang Mües" <wolfgang.mues@auerswald.de>
Subject: Re: Questions about NAND (double)bit errors
Date: Thu, 16 Feb 2006 22:08:54 +0000 [thread overview]
Message-ID: <20060216220854.GA27562@mail.shareable.org> (raw)
In-Reply-To: <200602161617.04905.manningc2@actrix.gen.nz>
Charles Manning wrote:
> > About bad block detection: what is your oppinion about partitioning the
> > flash (the programs in a read-only partition, the data in r/w).
>
> This gets fs specific. With YAFFS (and I assume JFFS2, but consult
> an expert), grabage collection will force read-only files to get
> rewritten occasionally. Thus for ultimate reliability it is
> probably a GoodIdea to seperate the read-only stuff into a seperate
> partition. This is also a GoodIdea in that a smaller partition
> mounts faster (true for YAFFS and JFFS2). So if all your kernel +
> mount stuff is seperated from your rw stuff things will probably dgo
> better.
Absolutely.
I've been testing 40 devices lately, and in 2 weeks, 5 of them (out of 40)
have corrupted files in JFFS2 when those files aren't being written.
I haven't seen any errors in the ROMFS partitions.
I'm still getting round to analysing the corrupt files / filesystems,
because that failure rate is too high even for configuration files
that are written from time to time.
These are 8MB chips, so presumably NOR.
-- Jamie
prev parent reply other threads:[~2006-02-16 22:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 11:12 Questions about NAND (double)bit errors Wolfgang Mües
2006-02-08 22:26 ` Charles Manning
2006-02-10 8:28 ` Wolfgang Mües
2006-02-14 14:10 ` Wolfgang Mües
2006-02-16 3:17 ` Charles Manning
2006-02-16 8:30 ` Wolfgang Mües
2006-02-16 22:08 ` Jamie Lokier [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=20060216220854.GA27562@mail.shareable.org \
--to=jamie@shareable.org \
--cc=linux-mtd@lists.infradead.org \
--cc=manningc2@actrix.gen.nz \
--cc=wolfgang.mues@auerswald.de \
/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