From: Artem Bityutskiy <dedekind1@gmail.com>
To: David Lambert <dave@lambsys.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Verify-after-write on sub-pages
Date: Sat, 29 Jan 2011 18:16:44 +0200 [thread overview]
Message-ID: <1296317804.2400.1.camel@localhost> (raw)
In-Reply-To: <4D41949D.2030505@lambsys.com>
On Thu, 2011-01-27 at 09:51 -0600, David Lambert wrote:
> I am working on a project that requires high reliability of logged data
> which is written to a UBI file system on NAND. I have observed one
> hardware failure mode at elevated temperatures where some chips report
> that a write was successful even though a subsequent read indicates that
> this was not true. To mitigate this I enabled
> CONFIG_MTD_NAND_VERIFY_WRITE. Unfortunately I found this does not work
> on sub-pages which are used by UBI. As a workaround I have forced UBI
> not to use sub-pages, but I was curious if either there were plans to
> add this feature, or if anyone was working on implementing it?
Yes, CONFIG_MTD_NAND_VERIFY_WRITE is broken sub-pages for very long
time. I doubt anyone is fixing this, you have a chance to do this :-)
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2011-01-29 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 15:51 Verify-after-write on sub-pages David Lambert
2011-01-29 16:16 ` 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=1296317804.2400.1.camel@localhost \
--to=dedekind1@gmail.com \
--cc=dave@lambsys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).