On Sat, Mar 20, 2010 at 11:07:14PM -0600, Randy Terbush wrote:
Can someone explain why the following different outputs from the two
mdadm --scan commands and which one is the appropriate entry in
mdadm.conf?
It is a display bug. it was fixed in commit
6e48d593c163e8107f06d13bc6092466a5d58c94
which is rolled into mdadm 3.1.2.
I'd upgrade to that from 3.1.1 anyway, due to the massive number of
fixes that went into 3.1.2.
mdadm --version
mdadm - v3.1.1 - 19th November 2009
# mdadm --examine --scan /dev/sd*
ARRAY /dev/md/0 metadata=1.1 UUID=b411b304:6385f171:26f07cb1:3c2b03de
name=hifi:0
# mdadm --detail --scan
ARRAY /dev/md0 metadata=1.01 name=hifi:0
UUID=b411b304:6385f171:26f07cb1:3c2b03de
metadata attribute being the primary difference.
The correct entry for mdadm.conf would be "1.1", but i believe "1.01" should
be understood as well.
L.
--
Luca Berra -- bluca@xxxxxxxxxx
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
