On Fri, May 06, 2011 at 03:50:59PM +0600, Roman Mamedov wrote: > On Fri, 6 May 2011 11:41:02 +0200 > Keld Jørn Simonsen <keld@xxxxxxxxxx> wrote: > > > > RAID1 is traditionally a mirror only setup (ok, some RAID > > > implementations may do some load-balancing of some sort). So a RAID1 > > > with 4 disks is one data set copied onto 4 disks. Bandwidth is roughly > > > the same as a single disk (ignoring any load balancing). > > > RAID10 is mirror and stripe. A RAID10 with 4 disks is similar to a 2 > > > disk RAID0 (double bandwidth with data split in half across both disks), > > > but with each disk having a mirror (which brings the total up to 4 drives). > > > > > > Additionally, a RAID1 disk (at least using MD) can be accessed just like > > > a normal disk (good for recovery etc.) however a single disk out of a > > > RAID10 array is next to useless. > > > > I think you are demonstrating some of my points about general knowledge > > quite nicely. Don't worry, you are not alone. > > So what is your proposal: people do not know they can do X, but commonly do Y, > so let's rename X to Y so that both things are called Y and they 'know how to > do it'? > > RAID10 is an established term and means "stripe of mirrors", period. > RAID1 means just a mirror. All the rest is just implementation details. > Trying to redefine 2x2 to be 5 as some 'educational project' is definitely > misguided. This is the common understanding: RAID10 means RAID1+0 - a RAID0 over two RAID1's. As you write. But in Linux MD, raid10 is something else. Something which is characterized as RAID1 in the SNIA RAID standards. raid10,offset is directly an implementation of one of the SNIA RAID1 variants. I am proposing that we call our raid10 layout types for RAID1 - in accordance with SNIA standards, and in accordance with the common understanding as demonstrated by you and others, even here on the linux-raid kernel mailing list. Best regards keld -- 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
