From: Artem Bityutskiy <dedekind1@gmail.com>
To: Peter Barada <peter.barada@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [YAFFS] bad block management policy
Date: Fri, 24 Aug 2012 14:44:38 +0300 [thread overview]
Message-ID: <1345808678.2848.290.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <5023C82B.3000007@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
On Thu, 2012-08-09 at 10:24 -0400, Peter Barada wrote:
> You could modify YAFFS to ignore -EUCLEAN returns from MTD which will
> prevent YAFFS from marking blocks bad prematurely, but then there is no
> way to predict when a block is about to wear out and return
> uncorrectable errors (-EBADMSG).
We recently improved this area and now you also can set the bitflip
threshold in the MTD so that MTD won't return -EUCLEAN unless the amount
of bits flipped is larger than the threshold. The idea is that UBI
scrubs eraseblocks (moves data to different ones) in case of bitflips.
But 1-bit flips happen so often on some devices, that it is wiser to
ignore those. So now the driver can set the level on which MTD will
start returning -EUCLEAN. Below that flip level, it will return 0.
So this also means that if you set the threshold = ECC strength, you
should never even get -EUCLEAN. Not sure it is good idea, but a
possibility as well.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-08-24 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 10:45 [YAFFS] bad block management policy peterlingoal
2012-08-09 14:24 ` Peter Barada
2012-08-09 14:55 ` peterlingoal
2012-08-24 11:44 ` Artem Bityutskiy [this message]
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=1345808678.2848.290.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=peter.barada@gmail.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 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.