To: linux-kernel@vger.kernel.org
From: Wiebe Cazemier <halfgaar@gmx.net>
Subject: Software RAID1 (with non-identical discs) performance
Date: Sat, 16 Dec 2006 13:39:22 +0100
Message-ID: <em0pdq$r7o$2@sea.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
User-Agent: KNode/0.10.4
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2271
Lines: 39

Hi,

I'm planning to put a software RAID1 array in my computer, but I have a few
technical questions. 

When using non-identical discs (not just size, but also geometry) to contruct
your array, you can never get the partitions of the underlying discs to be
equal in size because the size of a partition can only be N*cylindersize,
where cylindersize varies across discs; the array always assumes the size of
the smallest partition. When one of the discs fails, you need to replace it
and make a partition that is exactly equal in size to the array, but because
that usually is impossible, it mostly will be bigger. To cover for this, I
have always left a small bit of unpartioned space on my discs. This not only
provides me with headroom in making the partitions on discs with different
geometry, but it's also possible that brand B's 250 GB is a little smaller
than brand A's, and staying (well) below the 250 GB, makes sure any 250 GB
disc fits in the array.

My first question is, is this a necessary/convenient technique to ensure you
can replace discs over time, especially when you can't get the exact same
replacement disc?

My second question is about the performance impact of using non-identical discs
and partitions. I can't really find any info about this, but I've read someone
making the statement that it would slow things down.

My third question: write performance of RAID1 is usually lower than non-RAID,
because the data has to be sent over the bus twice. But, with for example an
NForce4 based mainboard using SATA, does that matter? I don't know if the SATA
ports are connected to the chipset by means of PCI express or hypertransport,
but both should be able to handle the double data transfer with room to spare.
So, as I understand it, as long as the kernel can perform both transfers
simultaniously, there should be no slow down, because when writing, there will
simply be two discs writing data simultaniously, at the same speed one drive
would. Is this correct?

Thanks in advance,

Wiebe Cazemier

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/