If I use mdadm 2.5.4 to create a version 1 superblock raid1 device, it
starts a resync. If I then reboot the computer part way through, when
it boots back up, the resync gets cancelled and the array is considered
clean. This is against a 2.6.18.1 kernel.
If I create a version 1 superblock raid1 array, mdadm -D <constituent
device> says that the device is not part of a raid array (and likewise
the kernel autorun facility fails to find the device).
If I create a version 1 superblock raid1 array, mdadm -E <constituent
device> sees the superblock. If I then run mdadm -E --brief on that
same device, it prints out the 1 line ARRAY line, but it misprints the
UUID such that is a 10 digit hex number: 8 digit hex number: 8 digit hex
number: 6 digit hex number. It also prints the mdadm device in the
ARRAY line as /dev/md/# where as mdadm -D --brief prints the device
as /dev/md#. Consistency would be nice.
Does the superblock still not store any information about whether or not
the array is a single device or partitionable? Would be nice if the
superblock gave some clue as to that fact so that it could be used to
set the auto= param on an mdadm -E --brief line to the right mode.
Mdadm assumes that the --name option passed in to create an array means
something in particular to the md array name and modifies subsequent
mdadm -D --brief and mdadm -E --brief outputs to include the name option
minus the hostname. Aka, if I set the name to firewall:/boot, mdadm -E
--brief will then print out the ARRAY line device as /dev/md//boot. I
don't think this is documented anywhere. This also raises the question
of how partitionable md devices will be handled in regards to their name
component.
--
Doug Ledford <dledford@xxxxxxxxxx>
GPG KeyID: CFBFF194
http://people.redhat.com/dledford
Infiniband specific RPMs available at
http://people.redhat.com/dledford/Infiniband
Attachment:
signature.asc
Description: This is a digitally signed message part
