public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@lazybastard.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org,
	Adrian Hunter <ext-adrian.hunter@nokia.com>
Subject: Re: JFFS2 wrong data CRC message
Date: Wed, 2 May 2007 15:51:33 +0200	[thread overview]
Message-ID: <20070502135133.GC20776@lazybastard.org> (raw)
In-Reply-To: <1178111184.2875.185.camel@pmac.infradead.org>

On Wed, 2 May 2007 14:06:24 +0100, David Woodhouse wrote:
> On Wed, 2007-05-02 at 16:02 +0300, Adrian Hunter wrote:
> > Unfortunately I started with an empty flash and have not rebooted at all.
> > 
> > I've been running stress tests constantly for about a week, and this is
> > the only JFFS2 message.  The tests do unmount and remount, but there are
> > no error messages.
> > 
> > So unless you can offer an alternative explanation I am going to have to
> > assume it is an error.
> 
> That's certainly possible -- and in fact is why I've resisted the
> persistent requests _not_ to print that message.

You could add a new node type to mark "safe" crc errors.  Something
roughly like this:
- Print error for crc errors, unless the next node in eraseblock is a
  "known crc error" node.
- Write "known crc error" node on mount for any node that is the last in
  an eraseblock if there still is enough room to write further data.

That should be able to eliminate most false positive.  If you care.

Jörn

-- 
The wise man seeks everything in himself; the ignorant man tries to get
everything from somebody else.
-- unknown

  reply	other threads:[~2007-05-02 13:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02  9:19 JFFS2 wrong data CRC message Adrian Hunter
2007-05-02 12:23 ` David Woodhouse
2007-05-02 13:02   ` Adrian Hunter
2007-05-02 13:06     ` David Woodhouse
2007-05-02 13:51       ` Jörn Engel [this message]
2007-05-02 14:00         ` David Woodhouse
2007-05-03  7:20       ` Adrian Hunter
2007-05-02 13:19     ` Vitaly Wool

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=20070502135133.GC20776@lazybastard.org \
    --to=joern@lazybastard.org \
    --cc=dwmw2@infradead.org \
    --cc=ext-adrian.hunter@nokia.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