On Thu, Jan 27, 2005 at 04:24:34PM +1100, Neil Brown wrote:
On Wednesday January 26, ryan@xxxxxxxxxxxxxxxxxxx wrote:
This bug that's fixed in 1.9.0, is in a bug when you create the array? ie
do we need to use 1.9.0 to create the array. I'm looking to do the same but
my bootdisk currently only has 1.7.soemthing on it. Do I need to make a
custom bootcd with 1.9.0 on it?
This issue that will be fixed in 1.9.0 has nothing to do with creating
the array.
It is only relevant for stacked arrays (e.g. a raid0 made out of 2 or
more raid1 arrays), and only if you are using
mdadm --assemble --scan
(or similar) to assemble your arrays, and you specify the devices to
scan in mdadm.conf as
DEVICES partitions
(i.e. don't list actual devices, just say to get them from the list of
known partitions).
actually the last statement is not true, a missing close(mdfd); causes
mdadm --assemble --scan to fail the first round even if you do specify
DEV /dev/mdX in mdadm.conf.
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
