From: Michael Rubin <mrubin@google.com>
To: Eric Sandeen <sandeen@redhat.com>, Jiaying Zhang <jiayingz@google.com>
Cc: tytso@mit.edu, Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH v4 0/3] dioread_nolock patch
Date: Fri, 15 Jan 2010 13:47:26 -0800 [thread overview]
Message-ID: <532480951001151347w2f1bf2b2j34bb88b58a766f9c@mail.gmail.com> (raw)
In-Reply-To: <4B50CD5B.9050804@redhat.com>
On Fri, Jan 15, 2010 at 12:17 PM, Eric Sandeen <sandeen@redhat.com> wrote:
> tytso@mit.edu wrote:
> At one point google was planning to devise a power-fail test
> harness. Any news on that?
We completed the tests. But there is good news and bad news. The good
news is that we were able to shake out a lot of bugs in the no journal
case (which have already been submitted upstream). We now can fairly
quickly and easily drive a lot of traffic to a system and then cut the
power, issue a panic or other event.
The bad news is that I was hoping to use open source tools to drive
the traffic. The goal would be to allow everyone to reproduce the
experiment. We got a little short handed on resources and ended up
using Google closed source workloads instead. This was mostly since we
were in a rush and able to get the network traffic up in one day with
those tools.
I was holding back on publishing the results since I was hoping we
would be able to generate traffic in a more open manner. But if you
are interested in the results anyway then give me or some one on the
team a day or two to dig them up.
In any case we have powerfail testing as part of our validation and
once Jiayingz is satisfied with the patch we will be running those
tests.
mrubin
--
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
next prev parent reply other threads:[~2010-01-15 21:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 19:30 [PATCH v4 0/3] dioread_nolock patch Theodore Ts'o
2010-01-15 19:30 ` [PATCH v4 1/3] ext4: mechanical change on dio get_block code in prepare for it to be used by buffer write Theodore Ts'o
2010-01-17 14:36 ` Aneesh Kumar K. V
2010-01-17 16:19 ` Eric Sandeen
2010-01-17 16:42 ` Aneesh Kumar K. V
2010-01-18 3:57 ` tytso
2010-01-15 19:30 ` [PATCH v4 2/3] ext4: use ext4_get_block_write in " Theodore Ts'o
2010-01-16 2:17 ` tytso
2010-01-17 14:21 ` Aneesh Kumar K. V
2010-01-18 5:25 ` Jiaying Zhang
2010-01-15 19:30 ` [PATCH v4 3/3] ext4: Use direct_IO_no_locking in ext4 dio read Theodore Ts'o
2010-01-17 14:19 ` Aneesh Kumar K. V
2010-01-15 19:39 ` [PATCH v4 0/3] dioread_nolock patch Ric Wheeler
2010-01-15 19:52 ` Eric Sandeen
2010-01-15 20:15 ` tytso
2010-01-15 20:17 ` Eric Sandeen
2010-01-15 21:47 ` Michael Rubin [this message]
2010-01-22 20:47 ` Valerie Aurora
2010-02-20 0:56 ` Michael Rubin
2010-02-23 0:36 ` Andreas Dilger
2010-02-16 21:07 ` Darrick J. Wong
2010-02-17 19:34 ` Jiaying Zhang
2010-02-19 21:25 ` Darrick J. Wong
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=532480951001151347w2f1bf2b2j34bb88b58a766f9c@mail.gmail.com \
--to=mrubin@google.com \
--cc=jiayingz@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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).