linux-ext4 - Re: breaking ext4 to test recovery

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4D9503C0.8080804@redhat.com>
Date:	Thu, 31 Mar 2011 17:44:16 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Andreas Dilger <adilger@...ger.ca>
CC:	Daniel Taylor <Daniel.Taylor@....com>, linux-ext4@...r.kernel.org
Subject: Re: breaking ext4 to test recovery

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
--
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