All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ohlsson, Fredrik (GE Healthcare, consultant)" <Fredrik.Ohlsson@ge.com>
To: <linux-ext4@vger.kernel.org>
Subject: ext4 settings in an embedded system
Date: Wed, 14 Nov 2012 11:41:59 +0100	[thread overview]
Message-ID: <C0489DC3A08C21449F8FE865472DC75204834F08@BUDMLVEM03.e2k.ad.ge.com> (raw)

Hi,
I would like to have advice regarding features and options.
I am working with an embedded system equipped with an IDE Flash Disk and the ext4 filesystem. I have identified 3 problems that I would like to solve in our product. The power is abruptly turned off from time to time, this has sometimes resulted in broken Superblock (inode8) and empty files with size 0 bytes. It also happens that file changes is not committed to disk even if minutes pass before a power loss. This is very undesirable and expensive in our case, we are searching for a solution or a workaround to the problems.
List with my problems I like to solve:
1. Broken Superblock (inode8).
2. Empty files, size 0.
3. Very long auto commit times, several minutes with default settings.


Is ext4 a bad choice for an embedded system with I 1Gb IDE Flash Disk and Debian 2.6.32-5-686?  Should we change filesystem?

I am planning to set the mount flags: barrier=1, commit=1 and data=journal, is this the way to go with an embedded system and ext4? 

Is there more ext4 options/settings I can use to get an embedded system reliable when a power loss occurs?

Best Regards

Fredrik Ohlsson
Software Engineer



--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2012-11-14 10:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 10:41 Ohlsson, Fredrik (GE Healthcare, consultant) [this message]
2012-11-14 20:51 ` ext4 settings in an embedded system Theodore Ts'o
2012-11-15  8:42 ` Artem Bityutskiy
2012-11-15 10:01   ` Andrey Sidorov
2012-11-15 10:38     ` Artem Bityutskiy
2012-11-16 15:40     ` Eric Sandeen
2012-11-19 10:42       ` Artem Bityutskiy
2012-11-16 15:44   ` Eric Sandeen
2012-11-19 10:43     ` Artem Bityutskiy
2012-11-16 15:56 ` Eric Sandeen
2012-11-16 16:18 Ohlsson, Fredrik (GE Healthcare, consultant)
2012-11-16 16:58 ` Eric Sandeen

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=C0489DC3A08C21449F8FE865472DC75204834F08@BUDMLVEM03.e2k.ad.ge.com \
    --to=fredrik.ohlsson@ge.com \
    --cc=linux-ext4@vger.kernel.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.