public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Massimo Calò" <m.calo@ctsgroup.it>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Data CRC failed on node...
Date: Mon, 16 Jun 2003 12:59:15 +0100	[thread overview]
Message-ID: <1055764754.2289.37.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <001001c333fb$3c2b3ba0$e10106c0@Massimo>

On Mon, 2003-06-16 at 12:34, Massimo Calò wrote:
> Hi All,
> 
>     I have a 5272 Motorola Coldfire based board, running "uClinux dist. :
> uClinux-20030305.tar.gz" +
> 
> "Tool Chain : m68k-elf-tools-20030314.sh.".
> 
> I have a 2Mb flash (AMD AM29LV160DB) using MTD + JFFS2.
> 
> It has worked fine for a long time, then I received the following message
> during the bootstarp :

>         jffs2_scan_inode_node(): Data CRC failed on node at 0x0005ca64: Read
> 0xb399e587c

That's normal and harmless. It's just a warning, not an error. You
powered down while a node was being written -- perhaps by the garbage
collection thread. In that case, the previous node containing the same
data will still be valid and will continue to be used. No data are lost.

> To fix the problem I do the command "eraseall /dev/mtd2" and the error was
> cleared.

Or you could have waited until the block containing the offending node
was garbage-collected, and it would have gone away on its own.

> Do I have to mount/unmount the flash every time I have to read/write from it
> ?

No, but if you want to avoid the cosmetic warnings, you should mount the
file system readonly or unmount it before each _reboot_.

-- 
dwmw2

      reply	other threads:[~2003-06-16 11:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-16 11:34 Data CRC failed on node Massimo Calò
2003-06-16 11:59 ` David Woodhouse [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=1055764754.2289.37.camel@passion.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=m.calo@ctsgroup.it \
    /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