linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tao Ma <tm@tao.ma>
To: Ric Wheeler <ricwheeler@gmail.com>
Cc: Andreas Dilger <adilger@dilger.ca>,
	Eric Sandeen <sandeen@redhat.com>,
	Daniel Taylor <Daniel.Taylor@wdc.com>,
	"linux-ext4@vger.kernel.org development"
	<linux-ext4@vger.kernel.org>,
	Johann Lombardi <johann@whamcloud.com>
Subject: Re: breaking ext4 to test recovery
Date: Sun, 03 Apr 2011 10:37:32 +0800	[thread overview]
Message-ID: <4D97DD6C.5090201@tao.ma> (raw)
In-Reply-To: <4D9718BB.2070005@gmail.com>

Hi Ric,
On 04/02/2011 08:38 PM, Ric Wheeler wrote:
> On 04/01/2011 10:15 PM, Andreas Dilger wrote:
>> On 2011-03-31, at 12:44 PM, Eric Sandeen wrote:
>>> 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?
>> I'm not sure what you mean.  Since the patch works at the block device
>> layer (in __generic_make_request()) it will drop the write at the time
>> it is submitted to the device, not when it is put into the cache.
>>
>> That said, I notice in the linux git repo a line that is in the same
>> place as our patch "if (should_fail_request(bio))" which looks like it
>> might have similar functionality when CONFIG_FAIL_MAKE_REQUEST is
>> enabled.  I'm not sure what kernel version it was added in.  It looks
>> like it is possible to fail the IOs some fraction of the time, or
>> permanently, by writing something into /sys/block/{dev}/fail.
>>
>> Cheers, Andreas
> 
> The device mapper developers are looking at having a device mapper
> target that can be used as a hot block cache - say given a S-ATA disk
> and a PCI-e SSD, you would store the hot blocks on the PCI-e card.
My topic in this year's lsf is "ssd and flashcache". I will talk about
how we use ssd and flashcache in our product system. And one of my
proposal is to rewrite it and get it merged into the upstream. So
you know anyone is working on this by now? I am glad that some other
guys have the same thought as me and we are happy to cooperate with
him/her to get it upstreamed ASAP.

Regards,
Tao

      parent reply	other threads:[~2011-04-03  2:37 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
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 [this message]

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=4D97DD6C.5090201@tao.ma \
    --to=tm@tao.ma \
    --cc=Daniel.Taylor@wdc.com \
    --cc=adilger@dilger.ca \
    --cc=johann@whamcloud.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=ricwheeler@gmail.com \
    --cc=sandeen@redhat.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).