public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Sergei Sharonov <sergei.sharonov@halliburton.com>
To: linux-mtd@lists.infradead.org
Subject: Re: NAND flash question
Date: Mon, 27 Jun 2005 21:57:20 +0000 (UTC)	[thread overview]
Message-ID: <loom.20050627T234825-377@post.gmane.org> (raw)
In-Reply-To: 200506271409.42449.charles.tilbury@comcast.net

Charles,
> I am using an ST Micro 64M byte x 8 bit flash part and JFFS2.  It mostly works 
> except that when the board reboots, JFFS2 reports CRC error messages when the 
> partition mounts again.  The strange part is that there does not seem to be 
> any data corruption or lost data.  Also, I do not see any error messages 
> while reading and writing.  However, the CRC errors seem to accumulate over 
> time.  Is there some way to prevent this from happening?  Repair it?  Should 
> I just ignore it?


In my experience these "errors" occur if you switch of the power without
proper shutdown. They are not errors really, just notes from JFFS2 that
some write was interrupted by power cycle or reset and the node written is
invalid. It is annoying but harmless. I believe they eventually go away
after the block is reclaimed by GC.

Sergei

  reply	other threads:[~2005-06-27 22:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-27 21:09 NAND flash question Charles Tilbury
2005-06-27 21:57 ` Sergei Sharonov [this message]
2005-06-28  7:23 ` Artem B. Bityuckiy
2005-06-28 15:58   ` Charles Tilbury
2005-06-28 16:06     ` Artem B. Bityuckiy
2005-06-28 16:41       ` Charles Tilbury
2005-06-28 18:30         ` David Woodhouse
2005-06-28 18:57           ` Charles Tilbury
2005-06-28 19:20             ` Sergei Sharonov
2005-06-29  6:39               ` Artem B. Bityuckiy
2005-06-29  6:29           ` Artem B. Bityuckiy

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=loom.20050627T234825-377@post.gmane.org \
    --to=sergei.sharonov@halliburton.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