Jon Nelson put forth on 1/31/2011 3:27 PM: > Before this goes any further, why not just reference the excellent > Wikipedia article (actually, excellent applies to both Wikipedia *and* > the article): > > http://en.wikipedia.org/wiki/Non-standard_RAID_levels#Linux_MD_RAID_10 > > The only problem I have with the wikipedia article is the assertion > that Linux MD RAID 10 is non-standard. It's as standard as anything > else is in this world. Unfortunately there is no organization, no standards body, that defines RAID levels. The use of the word "standard" in the article means "de facto" standard. All of the major and lesser expansion slot card and external RAID controller vendors have been using the same RAID level terminology for two decades. In this case, some have used "RAID 10" while others have used "RAID 1+0" for the same algorithm. Some used to use "RAID 10" and switched to using "RAID 1+0" recently o avoid perceived confusion in the marketplace. NONE of them include a RAID "10" or "1+0" implementation that works with only 3 disks, or even 2 disks. In the hardware industry, RAID "10" or "1+0" always means a stripe of mirrored pairs, 4 drives (devices) being the minimum required. I believe the "non standard" description is right on the money though because Linux mdraid is the only software/hardware solution that offers these other "layouts". The reason I disdain these multiple layouts has nothing to do with their technical merit, but the fact that it's almost impossible to discuss some things because we don't know what the heck each other are talking about. An OP may say "RAID 10" on this list, but is actually referring to one of the layouts that isn't the classic striped mirrors. Such as when discussing how many drives can fail and you're still up and running. That is well defined for traditional RAID 10, but not so well, at least from my perspective, for these "non standard" RAID 10 layouts. -- Stan -- 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
