From: Johannes Bauer <weolanwaybqm@spornkuller.de>
To: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Wear-leveling peculiarities
Date: Mon, 18 May 2015 22:38:12 +0200 [thread overview]
Message-ID: <555A4DB4.5050405@spornkuller.de> (raw)
In-Reply-To: <CAFLxGvxQeeA8dk7DY6ZcsAm0WBch7c6gOn92gUZB138B6bfeGA@mail.gmail.com>
Sorry Richard, I meant to reply to the list.
On 18.05.2015 19:58, Richard Weinberger wrote:
> Wear-leveling is done on UBI and UBIFS.
> What is CONFIG_MTD_UBI_WL_THRESHOLD set to?
Ooops. I honestly don't know, will check this out tomorrow. I must admit
that I wasn't aware of this setting at all.
> I suspect that your threshold was never reached.
Yes, I suspect you're right here.
>>From your provided graph it looks like all erase block have been
> erased t most 300 times.
> If your NAND starts dying after 300 erases you're in trouble.
And I fear you're right here as well
Although there's no definitive saying how many page writes the failed
units had because the defective sectors are so broken that the kernel
barfs out I/O errors. That means I can't even read the OOB metadata.
Cheers,
Johannes
next prev parent reply other threads:[~2015-05-18 20:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 13:53 Wear-leveling peculiarities Johannes Bauer
2015-05-18 14:09 ` Johannes Bauer
2015-05-18 17:58 ` Richard Weinberger
2015-05-18 17:59 ` Richard Weinberger
2015-05-18 20:38 ` Johannes Bauer [this message]
[not found] ` <555A4D38.3070702@spornkuller.de>
2015-05-18 20:47 ` Richard Weinberger
2015-05-26 9:38 ` Johannes Bauer
2015-05-26 10:08 ` Richard Weinberger
2015-05-26 11:14 ` Johannes Bauer
2015-05-26 16:19 ` Jeff Lauruhn (jlauruhn)
2015-05-26 16:24 ` Johannes Bauer
2015-05-26 16:29 ` Richard Weinberger
2015-05-26 18:20 ` Ezequiel Garcia
2015-05-19 9:17 ` valent.turkovic
2015-05-26 9:43 ` Johannes Bauer
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=555A4DB4.5050405@spornkuller.de \
--to=weolanwaybqm@spornkuller.de \
--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