From: Artem Bityutskiy <dedekind1@gmail.com>
To: Eric Sandeen <sandeen@redhat.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: Mon, 19 Nov 2012 12:43:56 +0200 [thread overview]
Message-ID: <1353321836.20111.36.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <50A65F64.3020603@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
On Fri, 2012-11-16 at 09:44 -0600, Eric Sandeen wrote:
> > I do not know for sure, but I doubt there is serious power-cut testing
> > regularly conducted for ext4, but people may correct me.
>
> We do it here, though maybe not as regularly as we should.
> I also periodically test journal replay, but not in a way that simulates
> lost write caches or misbehaving hardware. OTOH, those things are out
> of our control in the real world (if users disable barriers, or if the
> hardware lies to us).
Good to know, thanks. I actually now recall Josef mentioned that RedHad
does some power-cut testing.
> But you absolutely should test YOUR system, audit YOUR software, and
> YOUR configuration to be sure that it is behaving as you require.
Sure.
--
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:43 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
2012-11-16 15:44 ` Eric Sandeen
2012-11-19 10:43 ` Artem Bityutskiy [this message]
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=1353321836.20111.36.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=Fredrik.Ohlsson@ge.com \
--cc=linux-ext4@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).