All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Andrey Sidorov <qrxd43@motorola.com>
Cc: "Ohlsson, Fredrik (GE Healthcare,
	consultant)" <Fredrik.Ohlsson@ge.com>,
	linux-ext4@vger.kernel.org
Subject: Re: ext4 settings in an embedded system
Date: Thu, 15 Nov 2012 12:38:47 +0200	[thread overview]
Message-ID: <1352975927.2221.23.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CAA0+VHyODd+hsSL6FBqcLGb_r3ViHmL78ay=8k5CJeP0=Z2k7A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]

On Thu, 2012-11-15 at 13:01 +0300, Andrey Sidorov wrote:
> On Thu, Nov 15, 2012 at 12:42 PM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> 
> > We conducted some 3 years ago. Results were quite good for ext4 - in
> > many cases it could recover without a need to run ckfs.ext4, sometimes
> > it was not mountable, but ckfs.ext4 helped.
> >
> > On the opposite, ext3 constantly required ckfs.ext3, and sometimes died
> > so badly that even ckfs.ext3 could not recover it.
> 
> We ran about 6000 cycles of power resets with linux 2.6.37. The test
> was to run 3 tar processes unpacking linux kernel archive and power
> off after about 15 seconds. There were only 3 failures when file
> system couldn't be mounted, but that was due to HDD failure
> (unreadable sector in journal area). e2fsck successfully recovered
> those corruptions. As for software itself, there was no single issue
> and we never needed to run fsck after power loss. So I'd say that ext4
> is very tolerant to power losses at least in 2.6.37 assuming barriers
> and ordered data mode. I however understand this test is quite basic
> and any way results can be different for different kernels.

Very different experience indeed, shoes that everyone has to conduct own
power-cut tests in own system. I did not say that we were running on
eMMC.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-11-15 10:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14 10:41 ext4 settings in an embedded system Ohlsson, Fredrik (GE Healthcare, consultant)
2012-11-14 20:51 ` Theodore Ts'o
2012-11-15  8:42 ` Artem Bityutskiy
2012-11-15 10:01   ` Andrey Sidorov
2012-11-15 10:38     ` Artem Bityutskiy [this message]
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=1352975927.2221.23.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=Fredrik.Ohlsson@ge.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=qrxd43@motorola.com \
    /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.