From: David Updegraff <dave@cray.com>
To: linux-mtd@lists.infradead.org
Subject: nand oob corruption recovery
Date: Thu, 01 Jul 2004 12:24:13 -0500 [thread overview]
Message-ID: <40E448BD.8030909@cray.com> (raw)
I realize that specs say that if you wipe out mfg. bad block markers
that there is "no way to recover them".. but...
Are there suggestions for plausibly reliable test sequences that one
could run a nand chip thru to regenerate valid bad block markers?
Presumeably, it is insufficient to simply try to erase all blocks,
marking failures as bad... perhaps verified full page writes ?
Suggestions?
Thanks.
-dbu / Dave Updegraff / dave@cray.com
next reply other threads:[~2004-07-01 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 17:24 David Updegraff [this message]
2004-07-01 19:00 ` nand oob corruption recovery Thomas Gleixner
2004-07-01 22:45 ` David Updegraff
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=40E448BD.8030909@cray.com \
--to=dave@cray.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