From: Sergei Sharonov <sergei.sharonov@halliburton.com>
To: linux-mtd@lists.infradead.org
Subject: Re: Erasing NAND bad blocks?
Date: Wed, 10 Aug 2005 21:34:29 +0000 (UTC) [thread overview]
Message-ID: <loom.20050810T232947-784@post.gmane.org> (raw)
In-Reply-To: 200508110808.15354.manningc2@actrix.gen.nz
Charles,
> 2) Add a config in yaffs to not do any bad block marking during board bring
> up.
I suggest to disable retiring blocks that failed ECC on read. I see it happening
during power cycling. YAFFS leaks good blocks, e.g. disrupted write/erase
creates bad ECC and then GC retires perfectly good block. JFFS2 does not do that.
AFAIK, manufacturers suggest discarding only blocks that fail on write.
Sergei
next prev parent reply other threads:[~2005-08-10 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 16:41 Erasing NAND bad blocks? Steven Hein
2005-08-09 23:33 ` Thomas Gleixner
2005-08-10 20:08 ` Charles Manning
2005-08-10 21:34 ` Sergei Sharonov [this message]
2005-08-10 21:38 ` Thomas Gleixner
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=loom.20050810T232947-784@post.gmane.org \
--to=sergei.sharonov@halliburton.com \
--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