public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Martin Egholm Nielsen <martin@egholm-nielsen.dk>
To: linux-mtd@lists.infradead.org
Subject: Re: jffs2_get_inode_nodes(): Data CRC failed on NAND device
Date: Wed, 16 Feb 2005 08:38:42 +0100	[thread overview]
Message-ID: <cuut56$jl7$1@sea.gmane.org> (raw)
In-Reply-To: <1108497813.7801.12.camel@windu.rchland.ibm.com>

>>>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.
But this might be the better solution for Frederic, instead of poluting 
his code with fsync's. That is, just tune the /proc entry (which one?) 
to a value suitable for your needs - e.g. 2 secs.

>>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.
:o)

// Martin

  reply	other threads:[~2005-02-16  7:43 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 [this message]
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='cuut56$jl7$1@sea.gmane.org' \
    --to=martin@egholm-nielsen.dk \
    --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