From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ric Wheeler Subject: Re: Testing framework Date: Mon, 23 Apr 2007 18:11:09 -0400 Message-ID: <462D2EFD.4030507@emc.com> References: <2e4afe1e0704221346u6d6baec1uab88dc273ff08de9@mail.gmail.com> <1177337041.3704.4.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Karuna sagar K , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Avishay Traeger Return-path: Received: from mexforward.lss.emc.com ([128.222.32.20]:36340 "EHLO mexforward.lss.emc.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754311AbXDWWLT (ORCPT ); Mon, 23 Apr 2007 18:11:19 -0400 In-Reply-To: <1177337041.3704.4.camel@localhost> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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. > > > > 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