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

Estelle,

Thanks for this very fast answer !!!

Estelle HAMMACHE wrote:

>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.
>  
>
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 ?

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

>>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.
>  
>
It is an embedded board without power supervisor. I cannot detect when 
the customer power down the board :(

Frederic

  reply	other threads:[~2005-02-14 17:59 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 [this message]
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=4210E6C3.9030208@ateme.fr \
    --to=f.janot@ateme.fr \
    --cc=estelle.hammache@st.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.