> ok, so do I understand correctly that the initial raid-5 build only > writes data/parity to a single drive (the 'replacement')? Doing some > more testing now to see what I can find… Now, this is interesting. Initiating a raid-5 will create parity blocks (and perhaps data blocks) for the other drives, growing it will recreate parity for them all, which is normal. now, creating an empty raid-6 takes merely second, on the same (virtual) drive size (only more drives). What does the raid-6 code do that the raid-5 code could (or should?) have done? Vennlige hilsener / Best regards roy -- Roy Sigurd Karlsbakk (+47) 98013356 roy@xxxxxxxxxxxxx http://blogg.karlsbakk.net/ GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk. -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
