public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org, Bruce_Leonard@selinc.com
Subject: Re: For UBIFS users: be aware of write-back!
Date: Fri, 03 Oct 2008 10:45:46 +0300	[thread overview]
Message-ID: <1223019946.8051.45.camel@sauron> (raw)
In-Reply-To: <1223018149.3328.21.camel@macbook.infradead.org>


On Fri, 2008-10-03 at 08:15 +0100, David Woodhouse wrote:
> On Wed, 2008-10-01 at 08:51 +0300, Artem Bityutskiy wrote:
> > 
> > this e-mail informs about a quite important UBIFS feature which
> > have already confused many people.
> > 
> > If you use UBIFS, and especially if you have been using JFFS2 before,
> > please, read this documentation entry:
> > 
> > http://www.linux-mtd.infradead.org/doc/ubifs.html#L_writeback
> > 
> > Please, remember that UBIFS is _asynchronous_ FS. JFFS2 was synchronous,
> > so expect some of your old applications which were fine on JFFS2 to be
> > not ready to handle power cuts correctly in case of UBIFS.
> 
> JFFS2 wasn't synchronous on NAND. You still needed to use fsync() as
> appropriate to ensure that written data made it to the flash and not
> just to the write-buffer.

That's right, the above documentation even tells about this:

"In contrast, JFFS2 does not have write-back support and all the JFFS2
file system changes go the flash synchronously. Well, this is not
completely true and JFFS2 does have a small buffer of a NAND page size,
but it is small and we may treat JFFS2 as completely synchronous."

> Your list of things to think about is good, but it should be pointed out
> that it applies _generally_ to all systems and all file systems.

Right, agree. I'll amend the docs on the web site.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2008-10-03  7:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01  5:51 For UBIFS users: be aware of write-back! Artem Bityutskiy
2008-10-03  7:15 ` David Woodhouse
2008-10-03  7:45   ` Artem Bityutskiy [this message]
2008-10-03  7:57     ` David Woodhouse
2008-10-03  8:03       ` Artem Bityutskiy
2008-10-03  8:11   ` Artem Bityutskiy

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=1223019946.8051.45.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=Bruce_Leonard@selinc.com \
    --cc=dwmw2@infradead.org \
    --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