From: Artem Bityutskiy <dedekind1@gmail.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: linux-mtd-bounces@lists.infradead.org,
linux-mtd@lists.infradead.org, dwmw2@infradead.org,
philipp.zabel@gmail.com, Paul Parsons <lost.distance@yahoo.com>
Subject: Re: [PATCH] mtd: cfi: Wait for Block Erase operation to finish
Date: Tue, 13 Mar 2012 15:09:09 +0200 [thread overview]
Message-ID: <1331644149.3595.48.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <OF1F093251.0E93488C-ONC12579C0.0046E1EF-C12579C0.0046FAF5@transmode.se>
[-- Attachment #1: Type: text/plain, Size: 1843 bytes --]
On Tue, 2012-03-13 at 13:55 +0100, Joakim Tjernlund wrote:
> >
> > On Tue, 2012-03-13 at 09:27 +0100, Joakim Tjernlund wrote:
> > > >
> > > > On Fri, 2012-03-02 at 15:30 +0100, Joakim Tjernlund wrote:
> > > > > yes, UBI probably has some different use. One seems that it keeps
> > > > > erasing the
> > > > > same block over and over again if the erase fails. JFFS2 doesn't do
> > > > > that since
> > > > > you can't trust a block that is failing erase(how can you be sure that
> > > > > write will work?)
> > > > > So, IMHO, UBIFS should reconsider this policy.
> > > >
> > > > The thread is very long and I would like save my time by not going
> > > > through it. But if you could start a new thread and formulate the
> > > > problem with UBI, I could think about it a bit. I am open to change
> > > > policies if it is not too much work. Otherwise I am open to give hints
> > > > and suggestions and accept patches which change the policy. :-)
> > >
> > > I just noted from one of the logs Paul sent, it LOOKED like UBI tried
> > > to erase the same sector several times if erase failed, gave me the impression
> > > that UBI would try erasing a failing sector over and over again.
> > > I think Paul will have to provide details if this is the case or not.
> >
> > Correct, UBI does retry erasing several times, see function
> > 'do_sync_erase()' in drivers/mtd/ubi/io.c. Why would this be a problem?
>
> How can you trust a sector that fails to erase several times and then suddenly works ?
It could be a transient error, some random noise in the line, some
electrons did not want to move by an accident, something like this :-)
But I guess it does not make much sense for erase and write. For read it
does make sense to re-try. I am happy to accept a patch.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-03-13 13:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 17:22 [PATCH] mtd: cfi: Wait for Block Erase operation to finish Paul Parsons
2012-03-01 17:38 ` Paul Parsons
2012-03-01 17:53 ` Paul Parsons
2012-03-01 18:03 ` Joakim Tjernlund
2012-03-01 18:50 ` Paul Parsons
2012-03-02 12:39 ` Joakim Tjernlund
2012-03-02 14:06 ` Paul Parsons
2012-03-02 14:30 ` Joakim Tjernlund
2012-03-02 15:15 ` Paul Parsons
2012-03-09 10:45 ` Artem Bityutskiy
2012-03-13 8:27 ` Joakim Tjernlund
2012-03-13 12:48 ` Artem Bityutskiy
2012-03-13 12:55 ` Joakim Tjernlund
2012-03-13 13:09 ` Artem Bityutskiy [this message]
2012-03-13 13:33 ` Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2012-02-28 15:32 Paul Parsons
2012-02-28 21:25 ` Joakim Tjernlund
2012-02-29 0:23 ` Paul Parsons
2012-02-29 8:58 ` Joakim Tjernlund
2012-02-29 17:22 ` Paul Parsons
2012-02-29 18:03 ` Artem Bityutskiy
2012-02-29 22:26 ` Paul Parsons
2012-03-09 10:39 ` Artem Bityutskiy
2012-02-29 23:35 ` Joakim Tjernlund
2012-03-01 14:57 ` Paul Parsons
2012-03-01 15:59 ` Joakim Tjernlund
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=1331644149.3595.48.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-mtd-bounces@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=lost.distance@yahoo.com \
--cc=philipp.zabel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox