On Thursday January 10, [EMAIL PROTECTED] wrote:
> distro: Ubuntu 7.10
>
> Two files show up...
>
> 85-mdadm.rules:
> # This file causes block devices with Linux RAID (mdadm) signatures to
> # automatically cause mdadm to be run.
> # See udev(8) for syntax
>
> SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_FS_TYPE}=="linux_raid*", \
> RUN+="watershed /sbin/mdadm --assemble --scan --no-degraded"
....
>
> I see. So udev is invoking the assemble command as soon as it detects
> the devices. So is it possible that the spare is not the last drive to
> be detected and mdadm assembles too soon?
The "--no-degraded' should stop it from assembling until all expected
devices have been found. It could assemble before the spare is found,
but should not assemble before all the data devices have been found.
The "dmesg" trace you included in your first mail doesn't actually
show anything wrong - it never starts and incomplete array.
Can you try again and get a trace where there definitely is a rebuild
happening.
And please don't drop linux-raid from the 'cc' list.
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
