Accepted mdadm 2.6.2-1ubuntu1 (source)

[Jerome Haltom]

This should operate on a sort of fall back mechanism, assemble with
--no-degraded on udev events, but after a 2 minute timeout of some sort
waiting for root, try to assemble degraded arrays.

This doesn't mean the existing udev rules are not good. They are. But
policy also needs to exist someplace to handle the case of a degraded
array.

I would very much hate to reboot my server at my colo and have a drive
prevent it from booting. I'll send you a bill for the gasoline required
to go fix it. =)

On Wed, 2007-07-11 at 23:41 +0200, Reinhard Tartler wrote:
> Scott James Remnant <scott at ubuntu.com> writes:
> 
> > Accepted:
> >  OK: mdadm_2.6.2.orig.tar.gz
> >  OK: mdadm_2.6.2-1ubuntu1.diff.gz
> >  OK: mdadm_2.6.2-1ubuntu1.dsc
> >      -> Component: main Section: admin
> > Format: 1.7
> > Date: Wed, 11 Jul 2007 10:31:39 +0100
> > Source: mdadm
> > [...]
> >    * md activation:
> >      - We now have a single udev rule for both the real system and the
> >        initramfs, since doing things differently there will only result in bugs
> >        and confusion.
> >      - This rule runs "mdadm --assemble --scan --no-degraded", automatically
> >        activating any non-degraded device as their components are detected.
> 
> Does this mean that booting from a degraded array is no longer possible?
> 
> Suppose you have your root filesystem on an array, and one harddrive
> dies. Will the system boot, or will the boot process and in a busy box
> shell?
> 
> (I need to test this if I get the chance...)
> 
> Anyway, thanks a lot for fixing mdadm in ubuntu!
>