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
| ||
|
Date: Thu, 14 Jul 2011 08:59:21 +0200 From: Arne Jansen <sensille@....net> To: Ric Wheeler <rwheeler@...hat.com> CC: NeilBrown <neilb@...e.de>, Nico Schottelius <nico-lkml-20110623@...ottelius.org>, LKML <linux-kernel@...r.kernel.org>, Chris Mason <chris.mason@...cle.com>, linux-btrfs <linux-btrfs@...r.kernel.org>, Alasdair G Kergon <agk@...hat.com> Subject: Re: Mis-Design of Btrfs? On 14.07.2011 08:02, Ric Wheeler wrote: > On 07/14/2011 06:56 AM, NeilBrown wrote: >> I'm certainly open to suggestions and collaboration. Do you have in >> mind any >> particular way to make the interface richer?? > > If a file system uses checksumming or other data corruption detection > bits, it can detect that it got bad data on a write. If that data was > protected by RAID, it would like to ask the block layer to try to read > from another mirror (for raid1) or try to validate/rebuild from parity. > > Today, I think that a retry will basically just give us back a random > chance of getting data from a different mirror or the same one that we > got data from on the first go. Another case that comes to mind is the 'remove device' operation. To accomplish this, btrfs just rewrites all the data that reside on that device to other drives. Also, scrub and my recently posted readahead patches make heavy use of the knowledge of how the raid is laid out. Readahead always uses as many drives as possible in parallel, while trying to avoid unnecessary seeks on each device. -Arne > > Chris, Alasdair, was that a good summary of one concern? > > Thanks! > > Ric > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists