linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Rubin <mrubin@google.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Shaozhi Ye <yeshao@google.com>,
	linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Plans to evaluate the reliability and integrity of ext4 against power failures.
Date: Wed, 1 Jul 2009 10:39:49 -0700	[thread overview]
Message-ID: <532480950907011039m701bcfadwdd932e157badc1d5@mail.gmail.com> (raw)
In-Reply-To: <4A4AB49F.1070106@redhat.com>

On Tue, Jun 30, 2009 at 5:58 PM, Eric Sandeen<sandeen@redhat.com> wrote:
> Shaozhi Ye wrote:
> 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.

I am interested int he numbers too. As to the other dimensions, we
plan on investigating this as much as we can given our environment.

> 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.


Yup. We plan on detailing these qualities and comparing some of them
in the write up when yeshao's work is done.

> 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.

The end goal is to have a test suite for power loss that we can share
with the community. Realize we may send out numbers before sending out
the tests.

mrubin
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-07-01 17:39 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
2009-07-01 17:39   ` Michael Rubin [this message]
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=532480950907011039m701bcfadwdd932e157badc1d5@mail.gmail.com \
    --to=mrubin@google.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --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).