From: David Woodhouse <dwmw2@infradead.org>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2_get_inode_nodes(): Data CRC failed on NAND device
Date: Tue, 15 Feb 2005 00:03:06 +0000 [thread overview]
Message-ID: <1108425786.22597.6.camel@baythorne.infradead.org> (raw)
In-Reply-To: <1108404250.16612.327.camel@tglx.tec.linutronix.de>
On Mon, 2005-02-14 at 19:04 +0100, Thomas Gleixner wrote:
> On Mon, 2005-02-14 at 18:58 +0100, Frédéric Janot 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 ?
Yes. It's precisely the same as with other file systems. If you write to
a file, close it and then lose power immediately, your data may be lost.
It's not guaranteed to be on the medium until you sync.
> > 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 ?
>
> No, jffs2 does not write data just for fun. There is some application,
> script, daemon writing/modifying file(s).
Or garbage collection, but in that case no data are lost. It was just
copying from one part of the flash to another, and the old copy will
still be intact.
--
dwmw2
next prev parent reply other threads:[~2005-02-15 0:03 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 [this message]
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=1108425786.22597.6.camel@baythorne.infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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