On Sat, 28 Mar 2009, 11:52:59 +0100, Manfred Hollstein wrote:
Hi there,
On Fri, 27 Mar 2009, 22:42:08 +0100, Florian Gleixner wrote:
Hi,
i use this layout: /boot is on /dev/md0 mirror at the beginning of the 2 disks. lvm volumegroup is on /dev/md1 mirror / is a lvm volume swap and other filesystems are also lvm volumes.
mkinitrd creates a /etc/mdadm.conf inside the initrd that contains only the /dev/md1. The system stops when it it trying to check the /boot filesystem - because it is not found. When i add the /dev/md0 into the initrd mdadm.conf then booting works. Am i doing something wrong?
Which version of the OS is this with? I happened to face a similar issue when I added two additional disks and created a separate VG on the additional MD-raid1 device. The system stopped booting because mkinitrd decided that my root-fs is on the other MD device :-( The attached patch to /lib/mkinitrd/scripts/setup-md.sh fixed it for me. FWIW, this was on openSUSE-10.3
Actually attaching the patch would help...
Has anyone compared lvm mirroring vs. md mirroring? Reliability, performance, ...?
AFAIK, the MD code is much more mature than the dm-mirror stuff, and also has more features (write-intent bitmaps to reduce resync times, raid10, ...).
Thanks
Florian
HTH, cheers.
l8er manfred