From: Ric Wheeler <ric@emc.com>
To: Avishay Traeger <atraeger@cs.sunysb.edu>
Cc: Karuna sagar K <karunasagark@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Testing framework
Date: Mon, 23 Apr 2007 18:11:09 -0400 [thread overview]
Message-ID: <462D2EFD.4030507@emc.com> (raw)
In-Reply-To: <1177337041.3704.4.camel@localhost>
Avishay Traeger wrote:
> On Mon, 2007-04-23 at 02:16 +0530, Karuna sagar K wrote:
>> For some time I had been working on this file system test framework.
>> Now I have a implementation for the same and below is the explanation.
>> Any comments are welcome.
>
> <snip>
>
> You may want to check out the paper "EXPLODE: A Lightweight, General
> System for Finding Serious Storage System Errors" from OSDI 2006 (if you
> haven't already). The idea sounds very similar to me, although I
> haven't read all the details of your proposal.
>
> Avishay
>
It would also be interesting to use the disk error injection patches
that Mark Lord sent out recently to introduce real sector level
corruption. When your file systems are large enough and old enough,
getting bad sectors and IO errors during an fsck stresses things in
interesting ways ;-)
ric
next prev parent reply other threads:[~2007-04-23 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-22 20:46 Testing framework Karuna sagar K
2007-04-23 9:09 ` Kalpak Shah
2007-04-23 11:25 ` Karuna sagar K
2007-04-23 14:04 ` Avishay Traeger
2007-04-23 22:11 ` Ric Wheeler [this message]
2007-04-25 11:28 ` Karuna sagar K
2007-04-28 9:35 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2006-12-28 13:18 Karuna sagar k
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=462D2EFD.4030507@emc.com \
--to=ric@emc.com \
--cc=atraeger@cs.sunysb.edu \
--cc=karunasagark@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).