From: Josh Boyer <jdub@us.ibm.com>
To: Martin Egholm Nielsen <martin@egholm-nielsen.dk>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2_get_inode_nodes(): Data CRC failed on NAND device
Date: Tue, 15 Feb 2005 14:03:33 -0600 [thread overview]
Message-ID: <1108497813.7801.12.camel@windu.rchland.ibm.com> (raw)
In-Reply-To: <1108496777.7801.9.camel@windu.rchland.ibm.com>
On Tue, 2005-02-15 at 13:46 -0600, Josh Boyer wrote:
> On Tue, 2005-02-15 at 20:22 +0100, Martin Egholm Nielsen wrote:
> > Well, as someone told me the other day on the IRC-channel, the
> > writebuffer is flushed automatically if the buffer has not been accessed
> > for X (2?) seconds (controlled by the VFS, right?)...
> >
> > Correct me if I'm wrong...
>
> Not quite. The write buffer is flushed every 5 seconds, unless you tune
> it using the /proc entry. It's controlled by kupdated, which syncs the
> supers, which flushes the write buffer in JFFS2.
>
> If the write buffer contains GC data, that isn't flushed at all.
Just to clarify that, if the buffer contains _only_ GC data it isn't
flushed. If it contains GC + inode data, all of that data is.
josh
next prev parent reply other threads:[~2005-02-15 20:04 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 [this message]
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=1108497813.7801.12.camel@windu.rchland.ibm.com \
--to=jdub@us.ibm.com \
--cc=linux-mtd@lists.infradead.org \
--cc=martin@egholm-nielsen.dk \
/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