I can see what I did now. Very silly.
I created a RAID 5 with 4 disks then went about hot adding disks.
Silly me thinking it would increase the active space. Of course with
the parity being shared through the active disks this doesn't makes
sense.
I was wanting to define a systematic way that I could start with a
small number of disks and then expand the RAID as I needed more space
(and could afford more disks).
Is raidreconf the only way for reconfiguring a live system?
Cheers
--
Martin
"What we do in life, echoes in Eternity."
-Maximus Decimus Meridius
On Feb 05, 2006, at 21:40, Mark Hahn wrote:
Why can't I have more than 4 active drives in my md RAID?
why do you think you can't?
Why can't I easily migrate a RAID 0 to RAID 5. As I see it RAID 0 is
just RAID 5 with a failed parity check drive?
that would be raid3, actually. with r5, the parityblock rotates
among all drives.
$make
gcc -Wall -Werror -Wstrict-prototypes -DCONFFILE=\"/etc/mdadm.conf
\" -
ggdb -DSendmail=\""/usr/sbin/sendmail -t"\" -c -o super0.o super0.c
In file included from super0.c:31:
/usr/include/asm/byteorder.h:6:2: error: #warning using private
kernel header; include <endian.h> instead!
that's a bug in FC's includes, nothing to do with MD.
$make
gcc -Wall -Werror -Wstrict-prototypes -DCONFFILE=\"/etc/mdadm.conf
\" -
ggdb -DSendmail=\""/usr/sbin/sendmail -t"\" -c -o super0.o super0.c
cc1: warnings being treated as errors
super0.c: In function ‘add_internal_bitmap0’:
super0.c:737: warning: implicit declaration of function
‘__cpu_to_le32’
super0.c:742: warning: implicit declaration of function
‘__cpu_to_le64’
make: *** [super0.o] Error 1
I'd guess that MD sources should include -D__KERNEL__ in order to
get those functions, or else include its own definitions.
Oh just because I know it is going to be an issue I'm building on a
Athlon 64... my first 64bit linux box so I'm sure there are going to
be gotchas that I've not thought about.
LOTS of people have k8 boxes by now; it's not possible you're seeing
anything really new...
-
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
