From: Artem Bityutskiy <dedekind1@gmail.com>
To: Atlant Schmidt <aschmidt@dekaresearch.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
'Daniel Drake' <dsd@laptop.org>
Subject: RE: ubi vol_size and lots of bad blocks
Date: Fri, 14 Oct 2011 15:58:25 +0300 [thread overview]
Message-ID: <1318597112.12351.123.camel@sauron> (raw)
In-Reply-To: <0A40042D85E7C84DB443060EC44B3FD33001C1D733@dekaexchange07.deka.local>
On Tue, 2011-10-11 at 07:35 -0400, Atlant Schmidt wrote:
>
> Be careful here -- the last time I looked, blocks that go
> bad *ARE NOT* actually permanently marked as bad; they may
> no longer be used during the current boot, but the next time
> you reboot, they're eligible for attempted-but-often-failing
> use once again.
If this happened to you, this must be because of a bug in your MTD
driver. UBI dimply calls MTD mark_bad() function to mark blocks bad.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2011-10-14 12:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 12:09 ubi vol_size and lots of bad blocks Daniel Drake
2011-10-11 11:35 ` Atlant Schmidt
2011-10-14 12:58 ` Artem Bityutskiy [this message]
2011-10-14 13:03 ` Atlant Schmidt
2011-10-17 11:36 ` Atlant Schmidt
2011-10-14 11:15 ` Artem Bityutskiy
2011-10-17 13:35 ` Daniel Drake
2011-10-20 15:57 ` Artem Bityutskiy
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=1318597112.12351.123.camel@sauron \
--to=dedekind1@gmail.com \
--cc=aschmidt@dekaresearch.com \
--cc=dsd@laptop.org \
--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