All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Johannes Bauer <weolanwaybqm@spornkuller.de>,
	linux-mtd@lists.infradead.org
Subject: Re: Wear-leveling peculiarities
Date: Tue, 26 May 2015 12:08:13 +0200	[thread overview]
Message-ID: <5564460D.6010209@nod.at> (raw)
In-Reply-To: <f0e983ad35f8be37ef51686615017016@joe.dyn.spornkuller.de>

Am 26.05.2015 um 11:38 schrieb Johannes Bauer:
> Am 18.05.2015 22:47, schrieb Richard Weinberger:
> 
>>>> I suspect that your threshold was never reached.
>>>
>>> Yes, I suspect you're right here.
>>
>> If you did not set CONFIG_MTD_UBI_WL_THRESHOLD it is 4096.
>> So, regular wear-leveling did never happen.
> 
> Your initial assessment was correct. The WL_THRESHOLD is at 4096 when we should have configured it to a lower value for our NAND flash.
> 
>> The OOB-Data does not matter. UBI is not using OOB.
>>
>> So, you have to figure out why UBIFS is dying. Maybe it is a NAND issue.
> 
> Yes, sorry, I meant the EC header metadata. Indeed it looks like our NAND flash is dying because WL is not active. Determining the amount of erase-cycles of dead NAND blocks is
> difficult (since the EC header meatdata is lost as well when the whole block doesn't respond anymore).

What flash is this?
I should not start dying that early.

Thanks,
//richard

  reply	other threads:[~2015-05-26 10:08 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
     [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 [this message]
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=5564460D.6010209@nod.at \
    --to=richard@nod.at \
    --cc=linux-mtd@lists.infradead.org \
    --cc=weolanwaybqm@spornkuller.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.