Bug#344617: closed by martin f krafft <madduck@debian.org> (Re: Fwd: Re: userspace incorrectly detects RAID (d-i))

[Neil Brown]

On Thursday June 1, ehem at m5p.com wrote:
> > Unfortunately, this means that you have to recreate the arrays. At
> > least I do not know of a way to migrate version-0 to version-1.
> 
>           Magic : a92b4efc
>         Version : 00.90.00
>            UUID : 881b45c3:b1f47d8a:7b9b8401:167b0d02
> 
> Sigh, I take it 00.90.00 isn't sufficient? On the face of it writing such
> a conversion utility shouldn't be /too/ difficult, there that much to
> change?

No, 0.90.0 isn't sufficient.
I suspect one day
  mdadm --assemble --metadata=1 --update=metadata .....
will do what you want, but not today :-(

> 
> Having looked at it, since the devices have an indicator for where they
> are in the array (dev 0-nnn), that is also a good sanity test. In the
> case of a multiple detection of an array member never add the drive by
> default.

That would be fairly easy to implement.... it should be safe as long
as we only reject multiple devices if they have identical superblocks
(rather than just identical positions in the array, but one is older
than the other).... maybe this will be in 2.5.1

NeilBrown



> 
> > > So the correct fix if you are concerned about this it to use version-1
> > > metadata. 
> > >    --metadata=1
> > 
> > ... when creating new arrays.
> > 
> > Hopefully this will be the default soon.
> 
> The hardware transition might be a good time...
> 
> 
> -- 
> (\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
>  \BS (    |         EHeM at gremlin.m5p.com PGP 8881EF59         |    )   /
>   \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
>     \___\_|_/82 04 A1 3C C7 B1 37 2A*E3 6E 84 DA 97 4C 40 E6\_|_/___/
> 
> 
> 
> 
> 
> _______________________________________________
> pkg-mdadm-devel mailing list
> pkg-mdadm-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-mdadm-devel