public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Anders Grafstrom <grfstrm@users.sourceforge.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mtd/fs/jffs2 erase.c,1.84,1.85 roll back
Date: Sun, 25 Sep 2005 14:54:55 +0200	[thread overview]
Message-ID: <20050925125455.GA28978@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <43341DCD.6090002@users.sourceforge.net>

On Fri, 23 September 2005 17:22:53 +0200, Anders Grafstrom wrote:
> 
> jffs2 makes a second try if a failed erase is reported by the mtd 
> driver. But only for NAND (in jffs2_write_nand_badblock()). What I'm 
> after is a retry for NOR as well. But I wrote the patch so it would 
> retry for other cases of failure too.

Is a retry really an improvement?  When a block cannot be properly
erased on the first try, I would not trust it anymore.  Instead of a
retry, I'd rather mark it as a bad block and not touch it again.

Jörn

-- 
When you close your hand, you own nothing. When you open it up, you
own the whole world.
-- Li Mu Bai in Tiger & Dragon

  reply	other threads:[~2005-09-25 12:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1EHjUk-0001IT-Dn@phoenix.infradead.org>
     [not found] ` <43303409.5030406@users.sourceforge.net>
2005-09-20 16:48   ` mtd/fs/jffs2 erase.c,1.84,1.85 roll back Artem B. Bityutskiy
2005-09-20 19:49     ` Anders Grafstrom
2005-09-22 14:34       ` Artem B. Bityutskiy
2005-09-23 15:22         ` Anders Grafstrom
2005-09-25 12:54           ` Jörn Engel [this message]
2005-09-26  8:03             ` Artem B. Bityutskiy
2005-09-26  8:31               ` Jörn Engel

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=20050925125455.GA28978@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=grfstrm@users.sourceforge.net \
    --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