linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Worley <worleys@gmail.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: Wed, 1 Jul 2009 12:07:49 -0600	[thread overview]
Message-ID: <f3177b9e0907011107q17507be5icae2c1105faf4800@mail.gmail.com> (raw)
In-Reply-To: <d1c7fadd0906301627v44fa4a23x6b60726f8ce672c1@mail.gmail.com>

On Tue, Jun 30, 2009 at 5:27 PM, Shaozhi Ye<yeshao@google.com> 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.

This looks like a very valuable project.  I do lack understanding of
how certain problems that very much need to be tested will be tested.
>From your pdf:

       "Data loss: The client thinks the server has A while the server
does not."

I've been wondering how you test to assure that data committed to the
disk is really committed?

Ext4 receives the callback saying the data is committed; you need to
somehow log what it thinks has been committed and then cut power
without any time passing from the moment the callback was invoked,
then check the disk upon reboot to assure the data made it by
comparing it with the log.

I just don't see a method to test this, but it is so critically important.

Chris
>
> Thank you!
>
> --
> Shaozhi Ye
> Software Engineer Intern from UC Davis
> Cluster Management Team
> http://who/yeshao
>

  parent reply	other threads:[~2009-07-01 18:07 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
2009-07-01 18:07 ` Chris Worley [this message]
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=f3177b9e0907011107q17507be5icae2c1105faf4800@mail.gmail.com \
    --to=worleys@gmail.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).