All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Clouter <alex@digriz.org.uk>
To: linux-mtd@lists.infradead.org
Subject: Re: Filesystem advice
Date: Mon, 15 Feb 2010 23:54:02 +0000	[thread overview]
Message-ID: <qd3p47-jbg.ln1@chipmunk.wormnet.eu> (raw)
In-Reply-To: fcf894b71002151308i1a091f76rc6703734a0ea2164@mail.gmail.com

Volker Aßmann <volker.assmann@googlemail.com> wrote:
> 
> Sorry if this post is a bit off-topic for this mailing list, but this
> seams to be the best place to ask. We are currently using an embedded
> linux system with a compact flash drive and ext3 as a filesystem. Due
> to frequent power failures, we are often experiencing filesystem
> corruption problems, and thus want to replace this setup with a better
> option. My options / questions:
> 
> 1. Replace ext3 with UBIFS or JFFS2 using the MTD-Blockdevice
> emulation layer. Would this setup improve the reliability of our
> system with respect to power failures, and if yes which is better
> suited? Of course this approach would not improve the wear leveling,
> but would it make it worse / probably confuse the integrated flash
> controller?
>
....I always found mounting with 'sync' plus 'ro' in places that I could 
(along with liberal use of tmpfs) made for a very reliable setup.  That 
was for ext3.
 
I would be inclined to look at nilfs2 as it sounds like the type of 
thing you would be looking for?

> 3. In case both solutions are not viable, could you give an educated
> guess on which traditional filesystem would be better suited for this
> use case than ext3?
> 
Alot of corruption can be due to braindead userland expectations.  
Generally this means the userland tools need to learn about fsync().

Cheers

-- 
Alexander Clouter
.sigmonster says: Walk softly and carry a megawatt laser.

      reply	other threads:[~2010-02-16  0:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 21:08 Filesystem advice Volker Aßmann
2010-02-15 23:54 ` Alexander Clouter [this message]

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=qd3p47-jbg.ln1@chipmunk.wormnet.eu \
    --to=alex@digriz.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.