Chris MacKenzie <[email protected]> writes:
> I'm having a problem trying to do a simple re-organisation of my raid arrays
> for a private Xen system. The box in question is running Debian Lenny v5.02
> (AMD64).
[...]
> mdadm --stop /dev/md4
> mdadm -A /dev/md2 -m4 --update=super-minor /dev/sd[ab]2
>
> which works as expected, md4 is indeed stopped and a new array md2 shows as
> active in /proc/mdstat. I've modified the /etc/fstab file to reflect the
> change in swap location and edited /etc/mdadm/mdadm.conf, reboot and low and
> behold md4 is back and md2 is no where to be seen.
>
> Can anyone please give me a clue stick to hit this with ? :)
Assuming that you stop the array again before reboot, does the preferred minor
update in the superblock? Try stopping it, syncing, and checking that out?
Otherwise, is there a copy of the old mdadm.conf in the initramfs? Debian do
that, and use it to assemble arrays during boot. Maybe that needs rebuilding?
Finally, um, are you sure you want to rename them at all? You should be able
to use the /dev/disk/by-id/md-uuid-... labels or something like that to
address them portably, at which point it doesn't matter what the are called at
the bottom layer.
Daniel
--
✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
