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: Wed, 26 Aug 2009 00:20:58 -0400 From: Rik van Riel <riel@...hat.com> To: Pavel Machek <pavel@....cz> CC: david@...g.hm, Theodore Tso <tytso@....edu>, Ric Wheeler <rwheeler@...hat.com>, Florian Weimer <fweimer@....de>, Goswin von Brederlow <goswin-v-b@....de>, Rob Landley <rob@...dley.net>, kernel list <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...l.org>, mtk.manpages@...il.com, rdunlap@...otime.net, linux-doc@...r.kernel.org, linux-ext4@...r.kernel.org, corbet@....net Subject: Re: [patch] document flash/RAID dangers Pavel Machek wrote: > Lets say you are writing to the (healthy) RAID5 and have a powerfail. > > So now data blocks do not correspond to the parity block. You don't > yet have the corruption, but you already have a problem. > > If you get a disk failing at this point, you'll get corruption. Not necessarily. Say you wrote out the entire stripe in a 5 disk RAID 5 array, but only 3 data blocks and the parity block got written out before power failure. If the disk with the 4th (unwritten) data block were to fail and get taken out of the RAID 5 array, the degradation of the array could actually undo your data corruption. With RAID 5 and incomplete writes, you just don't know. This kind of thing could go wrong at any level in the system, with any kind of RAID 5 setup. Of course, on a single disk system without RAID you can still get incomplete writes, for the exact same reasons. RAID 5 does not make things worse. It will protect your data against certain failure modes, but not against others. With or without RAID, you still need to make backups. -- All rights reversed. -- 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
Powered by blists - more mailing lists