From: Artem Bityutskiy <dedekind1@gmail.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Andrey Sidorov <qrxd43@motorola.com>,
"Ohlsson, Fredrik (GE Healthcare,
consultant)" <Fredrik.Ohlsson@ge.com>,
linux-ext4@vger.kernel.org
Subject: Re: ext4 settings in an embedded system
Date: Mon, 19 Nov 2012 12:42:15 +0200 [thread overview]
Message-ID: <1353321735.20111.34.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <50A65E5D.7040305@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On Fri, 2012-11-16 at 09:40 -0600, Eric Sandeen wrote:
> Barriers were not made default on ext3 until 2011, in kernel v3.1,
> astonishingly. So it makes sense that ext3 fared worse than ext4.
Very probable, I do not remember if we had them. But we were testing on
top of eMMC with not write-cache.
Anyway, that was long time ago.
While on it, one problem I remember in an unrelated testing of ext3 on
top of eMMC was related to _read_ errors. Sometimes after an power cut
eMMC returned an ECC error, so a sector could be unreadable. But after
writing to this sector it became fine.
ext3 and the tools treated a read error as fatal. However, in case of
eMMC that was something "normal".
I do not know how the situation changes since then, this was probably in
2009.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-19 10:41 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
2012-11-16 15:40 ` Eric Sandeen
2012-11-19 10:42 ` Artem Bityutskiy [this message]
2012-11-16 15:44 ` Eric Sandeen
2012-11-19 10:43 ` Artem Bityutskiy
2012-11-16 15:56 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
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=1353321735.20111.34.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=Fredrik.Ohlsson@ge.com \
--cc=linux-ext4@vger.kernel.org \
--cc=qrxd43@motorola.com \
--cc=sandeen@redhat.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.