[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f3177b9e0907011107q17507be5icae2c1105faf4800@mail.gmail.com>
Date: Wed, 1 Jul 2009 12:07:49 -0600
From: Chris Worley <worleys@...il.com>
To: Shaozhi Ye <yeshao@...gle.com>
Cc: linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
fs-team@...gle.com
Subject: Re: Plans to evaluate the reliability and integrity of ext4 against
power failures.
On Tue, Jun 30, 2009 at 5:27 PM, Shaozhi Ye<yeshao@...gle.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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists