Can't rebuild RAID5?

1998-10-24 Thread Stephen Costaras
I have a RAID5 array comprised of 8 scsi disks (/dev/sd[b-i]1) with /dev/sdb1 being the first disk of the array. I'm using raidtools-0.51 under kernel 2.0.35. The first disk /dev/sdb1 failed. the raid continues as normal like it should. Now when I try to replace the disk with another fresh 4g

md5 becomes mdf when mdadd'ed under 2.1.135 -- expected ?

1998-10-24 Thread Piete Brooks
[ I'm not on the list, so please ensure you reply to me directly, and feel free to point me at TFM to R ... ] Using 2.1.125 "out of the box", I manually edited MAX_MD_DEV in include/linux/md.h to allow more devices -- is there any other way to do this? Anyway, it all works just fine for the bo

Is this bad?

1998-10-24 Thread Craig W. Hansen
I've been testing my first RAID5 array, using Linux 2.1.124 and the latest alpha raidtools and patch from 10/5. Everything looks fine, but when I did a big directory copy using the GNU "time" command, like this: craig:/raid# time cp -ar bigdir bigdir.tmp I get this output: 0.06user 13.50syste