public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Estelle HAMMACHE <estelle.hammache@st.com>
To: "Frédéric Janot" <f.janot@ateme.fr>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2_get_inode_nodes(): Data CRC failed on NAND device
Date: Mon, 14 Feb 2005 18:24:43 +0100	[thread overview]
Message-ID: <4210DEDB.DD35E2DE@st.com> (raw)
In-Reply-To: 4210DB19.9000808@ateme.fr

Frédéric Janot wrote:
> 
> Hi,
> 
> I have a board with samsung K9F5608UOC nand flash and mpc5200 ppc processor.

JFFS2 on NAND flash uses a page buffer. It is flushed to the flash when
it is full, or when you do fsync, sync or umount.

> when I reboot the board or when I remove the power "violently"

Some data may remain in the page buffer and is never written
to the Flash.

> jffs2_get_inode_nodes(): Data CRC failed on node at 0x00cc0f90: Read
> 0x6e17981a,  calculated 0x4614a389

Well obviously a node was partly written to flash and the end of the
node remained in the cache and was never written. This means you
lost some data.

> /And I get one more message each time I reboot the board. But the
> filesystem doesn't seem corrupted.

It is a warning only. The remainder of the file system will probably
still work. Only the last operation(s) before reboot are lost.

> If I umount / before rebooting, I don't have one more error message at
> the next reboot.

This is correct procedure if you don't want to lose any data.

> Do you have any idea about where the problem could come from ?

There is no problem. This is standard JFFS2 processing. Nodes with
wrong CRCs (partly written for instance) are ignored and not taken 
in account when building the FS tree and files.

Estelle

  reply	other threads:[~2005-02-14 17:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14 17:08 jffs2_get_inode_nodes(): Data CRC failed on NAND device Frédéric Janot
2005-02-14 17:24 ` Estelle HAMMACHE [this message]
2005-02-14 17:58   ` Frédéric Janot
2005-02-14 18:04     ` Thomas Gleixner
2005-02-15  0:03       ` David Woodhouse
2005-02-15 19:22         ` Martin Egholm Nielsen
2005-02-15 19:46           ` Josh Boyer
2005-02-15 20:03             ` Josh Boyer
2005-02-16  7:38               ` Martin Egholm Nielsen
2005-02-14 18:08     ` Josh Boyer

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=4210DEDB.DD35E2DE@st.com \
    --to=estelle.hammache@st.com \
    --cc=f.janot@ateme.fr \
    --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