[RFC] Dealing with mdadm superblock metadata default change

martin f krafft madduck at debian.org
Thu Feb 11 22:52:35 UTC 2010


also sprach Frans Pop <elendil at planet.nl> [2010.02.12.0427 +1300]:
> This seems to be causing some problems.

I am aware, but going to a conference right now and flying back to
Europe next week, so I am unlikely going to be able to do much about
it for now.

> 1) offer the choice to users
> I see from the Lenny mdadm man page that there are 4 (!) different metadata 
> versions: 0.90, 1.0, 1.1 and 1.2.
> - Is there any reason to allow users to choose between those (for Squeeze)?
> - If so, should all 4 versions be offered or only 0.90 and 1.2?

I think they should all be offered, but I think we should make 0.9
the default for squeeze and move to 1.1 only afterwards, once
grub-pc knows how to deal with it.

> Main problem is that we don't know how an array will be used at
> the time the choice will be made. A user may or may not create
> a separate /boot partition on a regular partition.

mdadm does warn about /boot on array creation btw.

-- 
 .''`.   martin f. krafft <madduck at d.o>      Related projects:
: :'  :  proud Debian developer               http://debiansystem.info
`. `'`   http://people.debian.org/~madduck    http://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems
 
"i love deadlines. i like the whooshing
 sound they make as they fly by."
                                                      -- douglas adams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/)
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20100212/c9a1e28d/attachment.pgp>


More information about the pkg-mdadm-devel mailing list