From: Ivan Djelic <ivan.djelic@parrot.com>
To: "Jean-Sébastien Gagnon" <jsgagnon@vizimax.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS recovery fails
Date: Tue, 18 Oct 2011 17:32:36 +0200 [thread overview]
Message-ID: <20111018153236.GA10466@parrot.com> (raw)
In-Reply-To: <225442585F89274EA3A62F88671ECBAC0D33C8EB@prod-svr-1.intranet.str.ca>
On Tue, Oct 18, 2011 at 04:10:32PM +0100, Jean-Sébastien Gagnon wrote:
> The situation you described should be already handled correctly by UBIFS, if the nand driver is correctly reporting pages with bitflips with the -EUNCLEAN. In this case, UBI will move the PEB to a new one as soon as possible to avoid this problem.
This would be true, if you could assume that a page reading failure always
occurs after a previous read on the same page reports an ecc correction.
But this is not the case: we had several unstable pages going from 0 bitflips
(perfect read) to 2 bitflips (failed read). No way to detect any failure, no
way to scrub data before it's too late.
And the answer from the manufacturer was: you should not use any partially
programmed/erased pages anyway, those should be cleaned up after recovering
from a power failure.
> My comment was really about the original error posted by Daniel Kuhn :
I agree on your comment about blank page; bitflips on erased space should be
corrected, or the upper layers should be robust to them...
BR,
--
Ivan
next prev parent reply other threads:[~2011-10-18 15:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 13:29 UBIFS recovery fails Daniel Kuhn
2011-10-17 20:17 ` Artem Bityutskiy
2011-10-18 8:11 ` Ricard Wanderlof
2011-10-18 8:42 ` Ivan Djelic
2011-10-20 16:37 ` Artem Bityutskiy
2011-10-20 16:36 ` Artem Bityutskiy
2011-10-18 8:29 ` Ivan Djelic
2011-10-19 15:15 ` Artem Bityutskiy
2011-10-19 17:27 ` Ivan Djelic
2011-10-18 12:47 ` Jean-Sébastien Gagnon
2011-10-18 14:54 ` Ivan Djelic
2011-10-18 15:10 ` Jean-Sébastien Gagnon
2011-10-18 15:32 ` Ivan Djelic [this message]
2011-10-18 16:05 ` Jean-Sébastien Gagnon
2011-10-19 6:50 ` Ricard Wanderlof
2011-10-19 10:22 ` Ivan Djelic
2011-10-19 12:17 ` Atlant Schmidt
2011-10-19 12:52 ` Ricard Wanderlof
2011-10-19 13:30 ` Atlant Schmidt
2011-10-20 16:43 ` Artem Bityutskiy
2011-10-24 7:00 ` Ricard Wanderlof
2011-10-29 19:43 ` Artem Bityutskiy
2011-10-20 14:14 ` Artem Bityutskiy
2011-10-18 15:29 ` Daniel Kuhn
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=20111018153236.GA10466@parrot.com \
--to=ivan.djelic@parrot.com \
--cc=jsgagnon@vizimax.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 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.