Richard Scobie wrote:
Have a look at the Grow Mode section of the mdadm man page.
Thanks! I overlooked that, although I did look at the man page before
posting.
It looks as though you should just need to use the same command you
used to grow it to 3 drives, except specify only 2 this
On Sun, Sep 09, 2007 at 09:31:54PM -1000, J. David Beutel wrote:
[EMAIL PROTECTED] ~]# mdadm --grow /dev/md5 -n2
mdadm: Cannot set device size/shape for /dev/md5: Device or resource busy
mdadm - v1.6.0 - 4 June 2004
Linux 2.6.12-1.1381_FC3 #1 Fri Oct 21 03:46:55 EDT 2005 i686 athlon i386
The 'degraded' attribute is useful to quickly determine if the array is
degraded, instead of parsing 'mdadm -D' output or relying on the other
techniques (number of working devices against number of defined devices, etc.).
The md code already keeps track of this attribute, so it's useful to export
Hello list,
I just created a RAID1 array consisting of two disks. After experiments with
processes *reading* from the device (badblocks, dd) and the iostat program, I
can see that only one disk is being utilised for reading. To be exact, every
time I execute the command one of the two disks
On Monday 10 September 2007 22:35:30 Iustin Pop wrote:
On Mon, Sep 10, 2007 at 10:29:30PM +0300, Dimitrios Apostolou wrote:
Hello list,
I just created a RAID1 array consisting of two disks. After experiments
with processes *reading* from the device (badblocks, dd) and the iostat
I'm having some troubles with the system below:
Linux inhale 2.6.18-4-amd64 #1 SMP Thu May 10 01:01:58 UTC 2007 x86_64 GNU/Linux
md2 is a
md2 : active raid1 sda3[0] sdb3[1]
484359680 blocks [2/2] [UU]
sda and sdb are both
Vendor: ATA Model: ST3500630AS Rev: 3.AA
Type:
There are many questions on the mailing list about the RAID1 read
performance profile. This patch adds a new paragraph to the RAID1
section in md.4 that details what kind of speed-up one should expect
from RAID1.
Signed-off-by: Iustin Pop [EMAIL PROTECTED]
---
this patch is against the git tree
