From: David Woodhouse <dwmw2@infradead.org>
To: "Stephen Bardsley" <sbardsley@rlwinc.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: bad block recovery
Date: Mon, 18 Mar 2002 13:02:43 +0000 [thread overview]
Message-ID: <29597.1016456563@redhat.com> (raw)
In-Reply-To: <PCEBLNKIDOKLBPDJECFEEEBBDHAA.sbardsley@rlwinc.com>
sbardsley@rlwinc.com said:
> My understanding is that the chip is now "unreliable", which I can
> live with for now. Does unreliable mean I can still use the chip if I
> can somehow format it?
Yes. Blocks can go bad during normal operation, and we have to be able to
deal with that case _anyway_. My nftl_format program can be made to do some
primitive tests on each erase block, and mark the completely broken ones as
such before formatting. But (for the benefit of the peanut gallery) you
should _only_ use nftl_format if you have already lost your bad block list.
--
dwmw2
next prev parent reply other threads:[~2002-03-18 12:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 12:54 bad block recovery Stephen Bardsley
2002-03-18 13:02 ` David Woodhouse [this message]
2002-03-18 13:31 ` Stephen Bardsley
2002-03-18 13:52 ` David Woodhouse
2002-03-18 15:51 ` Stephen Bardsley
2002-03-18 16:09 ` Stephen Bardsley
-- strict thread matches above, loose matches on Subject: below --
2002-04-06 5:05 Sulung Chang
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=29597.1016456563@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sbardsley@rlwinc.com \
/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