NeilBrown wrote:
that make them look like part of some old array.
Why jaunty partially assembled them isn't clear. Maybe it
is using --incremental and it is waiting for the rest of the
array to appear.
In my experience mdadm --incremental just doesn't work on Jaunty.
When you run it on the first disk in the raid it sets the raid up as
waiting for the rest, creates the /dev/md/xxx device, all looks good.
When you try the second disk (I have a raid-1) it complains that the
/dev/md/xxx exists and does nothing.
Results - exactly as "fibre raid" complains - you're left with a partly
set up inactive raid.
Haven't got around to doing a bugreport yet as I don't want to mess with
my running server.
--
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
