From: Artem Bityutskiy <dedekind1@gmail.com>
To: Atlant Schmidt <aschmidt@dekaresearch.com>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: RE: I don't understand how the counter for erasures is being maintained during erase failures
Date: Thu, 14 Apr 2011 13:55:09 +0300 [thread overview]
Message-ID: <1302778509.2796.17.camel@localhost> (raw)
In-Reply-To: <0A40042D85E7C84DB443060EC44B3FD328119F6E88@dekaexchange07.deka.local>
On Thu, 2011-04-14 at 06:53 -0400, Atlant Schmidt wrote:
> But the question I'll start-off with is: What specific
> step(s) is/are necessary to cause UBI to permanently
> consider this a bad block?
When you fail to erase it or when torture test fails, AFAIR. Just find
all callers of 'ubi_io_mark_bad()'.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-04-14 10:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 12:57 I don't understand how the counter for erasures is being maintained during erase failures Atlant Schmidt
2011-04-14 7:13 ` Artem Bityutskiy
2011-04-14 10:53 ` Atlant Schmidt
2011-04-14 10:55 ` Artem Bityutskiy [this message]
2011-04-14 10:58 ` Atlant Schmidt
2011-04-14 11:35 ` Artem Bityutskiy
2011-04-14 11:53 ` Atlant Schmidt
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=1302778509.2796.17.camel@localhost \
--to=dedekind1@gmail.com \
--cc=aschmidt@dekaresearch.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