From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Daniel Taylor <Daniel.Taylor@wdc.com>, linux-ext4@vger.kernel.org
Subject: Re: breaking ext4 to test recovery
Date: Thu, 31 Mar 2011 17:44:16 -0500 [thread overview]
Message-ID: <4D9503C0.8080804@redhat.com> (raw)
In-Reply-To: <6617927D-7C9C-4D02-97FD-C9CC75609448@dilger.ca>
On 3/31/11 5:21 PM, Andreas Dilger wrote:
> We have a kernel patch "dev_read_only" that we use with Lustre to
> disable writes to the block device while the device is in use. This
> allows simulating crashes at arbitrary points in the code or test
> scripts. It was based on Andrew Morton's test harness that he used
> for ext3 recovery testing back when it was being ported to the 2.4
> kernel.
>
> http://git.whamcloud.com/?p=fs/lustre-release.git;a=blob_plain;f=lustre/kernel_patches/patches/dev_read_only-2.6.32-rhel6.patch;hb=HEAD
>
> The best part of this patch is that it works with any block device,
> can simulate power failure w/o any need for automated power control,
> and once the block device is unused (all buffers and references
> dropped) it can be re-activated safely.
It won't simulate a lost write cache though, will it?
-Eric
next prev parent reply other threads:[~2011-03-31 22:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 2:45 breaking ext4 to test recovery Daniel Taylor
2011-03-29 3:10 ` Tao Ma
2011-03-29 13:50 ` Eric Sandeen
2011-03-29 14:33 ` Rogier Wolff
2011-03-29 17:33 ` Greg Freemyer
2011-03-29 22:26 ` Daniel Taylor
2011-03-29 22:33 ` Eric Sandeen
2011-03-31 22:11 ` Andreas Dilger
2011-03-31 22:22 ` Andreas Dilger
2011-03-31 22:21 ` Andreas Dilger
2011-03-31 22:44 ` Eric Sandeen [this message]
2011-04-01 15:26 ` Lukas Czerner
2011-04-01 15:52 ` Ric Wheeler
2011-04-02 2:15 ` Andreas Dilger
2011-04-02 12:38 ` Ric Wheeler
2011-04-02 18:50 ` Andreas Dilger
2011-04-03 2:37 ` Tao Ma
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=4D9503C0.8080804@redhat.com \
--to=sandeen@redhat.com \
--cc=Daniel.Taylor@wdc.com \
--cc=adilger@dilger.ca \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.