I have raid0-over-raid1 using four SCSI disks:
md3 : active raid0 md/2[1] md/1[0]
71681536 blocks 128k chunks
md1 : active raid1 scsi/host1/bus0/target1/lun0/part1[1]
scsi/host1/bus0/target0/lun0/part1[0]
35840896 blocks [2/2] [UU]
md2 : active raid1 scsi/host1/bus0/target3/lun0/part1[1]
scsi/host1/bus0/target2/lun0/part1[0]
35840896 blocks [2/2] [UU]
I cannot use mdadm to examine the underlying raid1 sets. When I use
'mdadm --examine /dev/md/1' and 'mdadm --examine /dev/md/2', I see the
same UUID and a raid level 0. This is the correct information for
md/3. 'mdadm --examing /dev/md/3' doesn't work. It says:
mdadm: No super block found on /dev/md/3 (Expected magic a92b4efc, got
77315132).
mdadm comes with so little documentation, I cannot determine if this is
the expected behavior.
-jwb
-
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
