From: Eric Sandeen <sandeen@redhat.com>
To: Shaozhi Ye <yeshao@google.com>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
fs-team@google.com
Subject: Re: Plans to evaluate the reliability and integrity of ext4 against power failures.
Date: Tue, 30 Jun 2009 19:58:07 -0500 [thread overview]
Message-ID: <4A4AB49F.1070106@redhat.com> (raw)
In-Reply-To: <d1c7fadd0906301627v44fa4a23x6b60726f8ce672c1@mail.gmail.com>
Shaozhi Ye wrote:
> Hi there,
>
> We are planing to evaluate the reliability and integrity of ext4
> against power failures and will post the results when its done.
> Please find attached design document and let me know if you have any
> suggestions for features to test or existing benchmark tools which
> serve our purpose.
>
> Thank you!
>
I'll be very interested to see the results. One thing you will need to
look out for (people who know me knew I would say this ;) is volatile
write caches on the storage, and filesystem barrier implementation.
To characterize the test, you'll want to be explicit about your storage.
Are they local disks? A Raid controller? If the disks are external to
the server, is power lost to the disks? Do they have write caching
enabled? If so do write barriers from the filesystem pass through to
the storage? This will all be highly relevant to how a power loss will
affect the filesystem.
I'm also curious about whether the tool itself will be available under
an open source license? Other filesystems would benefit from this
testing as well.
Thanks,
-Eric
next prev parent reply other threads:[~2009-07-01 0:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 23:27 Plans to evaluate the reliability and integrity of ext4 against power failures Shaozhi Ye
2009-07-01 0:58 ` Eric Sandeen [this message]
2009-07-01 17:39 ` Michael Rubin
2009-07-01 18:07 ` Chris Worley
2009-07-01 18:31 ` Michael Rubin
2009-07-01 18:44 ` Ric Wheeler
2009-07-01 19:58 ` Jeff Moyer
2009-07-02 2:12 ` Jamie Lokier
2009-07-02 11:21 ` Ric Wheeler
2009-07-01 20:59 ` Theodore Tso
2009-07-02 1:04 ` Michael Rubin
2009-07-01 23:37 ` Andreas Dilger
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=4A4AB49F.1070106@redhat.com \
--to=sandeen@redhat.com \
--cc=fs-team@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=yeshao@google.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).