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: <A5567907-0FC9-4552-9282-F7B4B7E1113D@whamcloud.com>
Date:	Sat, 2 Apr 2011 08:50:38 -1000
From:	Andreas Dilger <adilger@...mcloud.com>
To:	Ric Wheeler <ricwheeler@...il.com>
Cc:	Eric Sandeen <sandeen@...hat.com>,
	Daniel Taylor <Daniel.Taylor@....com>,
	"linux-ext4@...r.kernel.org development" <linux-ext4@...r.kernel.org>,
	Johann Lombardi <johann@...mcloud.com>
Subject: Re: breaking ext4 to test recovery

On 2011-04-02, at 2:38 AM, Ric Wheeler <ricwheeler@...il.com> wrote:
> 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.

There was a patch posted around December called bcache which did this same thing. I don't recall if it was a DM  target or not. 

> What might be a great simulation would be to have a way to destroy that cache, assuming we could get a cache policy that simulates some reasonable, disk like caching policy :)

The one difficulty with DM targets is that they cannot be used with non DM devices. That was one of the advantages of EVMS (if anyone remembers that) - it could work with any existing block device. 

Cheers, Andreas
--
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