public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: linux-mtd@lists.infradead.org
Cc: Bruce_Leonard@selinc.com
Subject: For UBIFS users: be aware of write-back!
Date: Wed, 01 Oct 2008 08:51:28 +0300	[thread overview]
Message-ID: <1222840288.8051.24.camel@sauron> (raw)

Hi,

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.

Just an unsorted list of important items:

* Every time you write to a file, please, ask yourself: "if a
  power cut happens now, is it OK if I loose data or that my file may
  contain garbage or be inconsistent afterward? Is my application 
  ready to clean that up?"

* If your application changes a configuration file, you probably
  should use the "atomic file update" trick described at the web site.

* Keep the write-back issues in mind if you write scripts as
  well. In bash, use "sync" when needed. Smarter languages like
  Perl have more fine-grained and efficient calls.

Thanks.

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

             reply	other threads:[~2008-10-01  5:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01  5:51 Artem Bityutskiy [this message]
2008-10-03  7:15 ` For UBIFS users: be aware of write-back! David Woodhouse
2008-10-03  7:45   ` Artem Bityutskiy
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=1222840288.8051.24.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=Bruce_Leonard@selinc.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