Bug#344617: closed by martin f krafft <madduck@debian.org> (Re:
Fwd: Re: userspace incorrectly detects RAID (d-i))
Elliott Mitchell
ehem at m5p.com
Fri Jun 2 03:19:08 UTC 2006
>From martin f krafft <madduck at debian.org>:
> also sprach Neil Brown <neilb at suse.de> [2006.06.01.0427 +0200]:
> > This is fixed with version-1 superblocks.
>
> Thus this was fixed by upstream when I uploaded 2.4.1-1.
> > The version-1 metadata records the offset in the device of the
> > superblock. So if you find a superblock near the end of a device,
> > its address in that device is different from the number recorded
> > in the superblock, you know you found it in the wrong device.
>
> 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?
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.
> > 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\_|_/___/
More information about the pkg-mdadm-devel
mailing list