On 8 Mar 2002, Jeffrey W. Baker wrote:
> 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:
It's a little hard to understand at first, but the --examine option allows
you to view information about a member disk (including information foudn
in the md superblock).
So you can use 'mdadm --examine' on any member disk, or in this case an
array that also happens to be a member disk (/dev/md/1 and /dev/md/2).
You could also use the --examine feature on member disks of /dev/md/1 and
/dev/md/2 like:
mdadm -E /dev/scsi/host1/bus0/target0/lun0/part1
mdadm -E /dev/sdb1
> mdadm: No super block found on /dev/md/3 (Expected magic a92b4efc, got
> 77315132).
That's because you're trying to use an option that you should use on array
members, not arrays. Use --detail instead, which prints information about
an array:
# mdadm -D /dev/md3
/dev/md3:
Version : 00.90.00
Creation Time : Fri Mar 8 16:50:46 2002
Raid Level : raid0
Array Size : 35840512 (34 GiB)
Raid Disks : 2
Total Disks : 2
Preferred Minor : 3
Persistance : Superblock is persistant
Update Time : Fri Mar 8 16:50:46 2002
State : dirty, no-errors
Active Drives : 2
Working Drives : 2
Failed Drives : 0
Spare Drives : 0
Chunk Size : 128K
Number Major Minor RaidDisk State
0 9 1 0 active sync /dev/md1
1 9 2 1 active sync /dev/md2
UUID : 3aaa0122:29827cfa:5331ad66:ca767371
> mdadm comes with so little documentation, I cannot determine if this is
> the expected behavior.
I hope to get some out to the list and to Neil shortly. But, I'm
sidetracked with another (RAID book) project for right now.
---
Derek Vadala, derek@cynicism.com, http://www.cynicism.com/~derek
-
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
