public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@logfs.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-mtd@lists.infradead.org, "Jörn Engel" <joern@logfs.org>,
	"David Woodhouse" <dwmw2@infradead.org>,
	"Josh Boyer" <jwboyer@gmail.com>, Duke <ezbonites@gmail.com>
Subject: Re: jffs2: too few erase blocks
Date: Mon, 29 Oct 2007 22:54:58 +0100	[thread overview]
Message-ID: <20071029215457.GB1027@lazybastard.org> (raw)
In-Reply-To: <20071029205125.GA27773@mail.shareable.org>

On Mon, 29 October 2007 20:51:25 +0000, Jamie Lokier wrote:
> 
> When you say "sync", do fdatasync() / fsync() on open files and
> directories flush the necessary blocks from wbuf for those
> files/directories data and their inode metadata, for JFFS2?
> 
> I have been calling sync(), but I wonder if fdatasync/fsync do as they
> are supposed to?
> 
> (If you know about other fses like LogFS/Yaffs/UBIFS that would be
> handy, too).

fsync/fdatasync should work on logfs.  If you know a good way to test
this, I'd add it to my suite of regression tests.  Right now I have to
rely on reading the code.

> Probably all are unnecessary in my specific application, as I use a
> JFFS2 with cfi_cmdset_0002, which I get the impression doesn't buffer
> any writes anyway.  But I like to get the application code right, in
> case I change to another device.

Any filesystem should follow the standards here.  Anything else is a
bug.

Jörn

-- 
Victory in war is not repetitious.
-- Sun Tzu

  parent reply	other threads:[~2007-10-29 22:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 14:06 jffs2: too few erase blocks Duke
2007-10-25 14:22 ` Josh Boyer
2007-10-25 22:15   ` Jamie Lokier
2007-10-26 17:00     ` Duke
2007-10-26 21:02       ` Duke
2007-10-28 18:02         ` Jamie Lokier
2007-10-29  2:59           ` David Woodhouse
2007-10-29 14:38             ` Jörn Engel
2007-10-29 20:51               ` Jamie Lokier
2007-10-29 21:40                 ` David Woodhouse
2007-10-29 22:50                   ` Jamie Lokier
2007-10-29 21:54                 ` Jörn Engel [this message]
2007-10-29 22:46                   ` Jamie Lokier
2007-10-30 16:09                     ` Jörn Engel
2007-10-30 20:08                       ` Duke
2007-10-30 20:19                         ` Jörn Engel
2007-10-30 21:42                           ` Duke

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=20071029215457.GB1027@lazybastard.org \
    --to=joern@logfs.org \
    --cc=dwmw2@infradead.org \
    --cc=ezbonites@gmail.com \
    --cc=jamie@shareable.org \
    --cc=jwboyer@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox