Bug#361408: Further information

[Detlef Schmicker]

Hay,

I have my raids now up and running. It works with the strickt

$ cat /etc/mdadm/mdadm.conf
DEVICE partitions
CREATE owner=root group=disk mode=0660
ARRAY /dev/md0 level=raid1 num-devices=2 devices=/dev/hda2
ARRAY /dev/md1 level=raid1 num-devices=2 devices=/dev/hda3
ARRAY /dev/md2 level=raid1 num-devices=2 devices=/dev/hda1,/dev/hdc1

I was even able to start up with mdrun before I changed the mdadm.conf.

But I was not able to start with the tipp provided by mdrun
  /usr/share/mdadm/mkconf > /etc/mdadm/mdadm.conf
  mdadm --assemble --scan --auto=yes

as mkconf gives


sarge:/etc/mdadm# /usr/share/mdadm/mkconf
DEVICE partitions
CREATE owner=root group=disk mode=0660 auto=yes metadata=1
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=f00c2d56:12d94a71:7544ea96:bac045d0
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=bab67f93:8d6ae88c:a94069f9:03661a7a
ARRAY /dev/md2 level=raid1 num-devices=2
UUID=7f96e6c7:6f4e22b9:95d187de:8bb4fa04
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=8be3aeb5:6621388f:f8a154d8:ca63d2a6
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=53f86543:986d4080:3564d273:2586e4f0

It seems, that there exists extra old information in my raids. I have no
idea, how to remove. But more important, before the update to 2.4.1 the
never made problems. Even if it is my mistake, it will be a problem for
others in case of upgrade (from sarge to etch), because they will not
know about problems.

How can I clean up the devices. This procedure could be included in
upgrade?!

Thanks Detlef

-- 
Detlef Schmicker <d.schmicker at physik.de>