<snip> > 11 Seagate 180GB disks in software RAID5 config (note that > "Array Size" below looks suspicious -- overflowing?. also -- > why 13 disks when only 12 requested?) <snip> > Build with: mdadm --create /dev/md6 --chunk=128 --level=5 --raid-disks=12 > --spare-disks=0 /dev/sd[d-o]1 > /dev/md6: > Version : 00.90.00 > Creation Time : Sat Mar 9 14:34:17 2002 > Raid Level : raid5 > Array Size : -197258624 > Device Size : 177293184 (169 GiB) > Raid Disks : 12 > Total Disks : 13 > Preferred Minor : 6 > Persistance : Superblock is persistant > > Update Time : Sat Mar 9 14:34:17 2002 > State : dirty, no-errors > Active Drives : 11 > Working Drives : 12 > Failed Drives : 1 > Spare Drives : 1 I've seen this too. It has one spare drive even though you specify --spare-disks=0 on the commend line. That seems to be where the extra disk comes from. In my case the disk layout looked kinda weird when issuing "mdadm --detail /dev/mdX". That was the reson for the one failed drive, atleast in my case. Regards, Fredrik Lindgren - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
