Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Boyer <jdub@us.ibm.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 12:08:01 -0600	[thread overview]
Message-ID: <1108404481.7790.2.camel@windu.rchland.ibm.com> (raw)
In-Reply-To: <4210E6C3.9030208@ateme.fr>

On Mon, 2005-02-14 at 18:58 +0100, Frédéric Janot wrote:
> >
> Does that mean that I have to call fsync each time after fclose a file ?
> Even if I do not edit some files, I get this kind of error. Does that 
> mean something (jffs2 itself or other) write some data to the flash all 
> the time ?

Sorta.  See below.

> 
> >Some data may remain in the page buffer and is never written
> >to the Flash.
> >  
> >
> So I really loose some data :(

Maybe not.  It could be a GC node that was cut short.  In that case, you
shouldn't loose any data since the original node should still be in
place.

> It is an embedded board without power supervisor. I cannot detect when 
> the customer power down the board :(

If you are worried about data loss, then fsync/sync is probably what you
should do.

josh

      parent reply	other threads:[~2005-02-14 18:08 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
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 [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=1108404481.7790.2.camel@windu.rchland.ibm.com \
    --to=jdub@us.ibm.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