I grabbed the 2.2.14 tarball, and Ingo's patch this morning, and compiled up
a copy of 2.2.14 because I wanted to test the read balancing patch against
the stock 2.2.14 with Ingo's patch (they're not integrated yet, are they?).
The patch applied cleanly, and I compiled the kernel with all of the proper
options (AFAICT).  When I try to boot with the new kernel, I get:

md.c: sizeof(m_super_t) = 4096 <cr>
Autodetecting RAID Arrays <cr>
Autorun... <cr>
...autorun done. <cr>
Bad md_map in ll_rw_block isofs_read_super: bread failed, dev=09:01,
iso_blknum=16, block=32 <cr>
kernel panic: VFS: unable to open root fs on 09:01 <cr>

A three finger salute at this point will get a "stopping all md devices" and
a reboot.  Seems that 09:01 is /dev/md1.
Here's lilo.conf and raidtab.  I'm running an install of RH61 that was
installed onto a mirror.

=====lilo.conf=====

boot=/dev/md0
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=linux

image=/boot/bzImage-2.2.14
        label=linux
        read-only
        root=/dev/md1

image=/boot/vmlinuz-2.2.12-20
        label=linux.redhat
        initrd=/boot/initrd-2.2.12-20.img
        read-only
        root=/dev/md1

=====raidtab=====
raiddev             /dev/md0
raid-level                  1
nr-raid-disks               2
chunk-size                  64k
persistent-superblock       1
#nr-spare-disks     0
    device          /dev/sda5
    raid-disk     0
    device          /dev/sdb5
    raid-disk     1
raiddev             /dev/md1
raid-level                  1
nr-raid-disks               2
chunk-size                  64k
persistent-superblock       1
#nr-spare-disks     0
    device          /dev/sda6
    raid-disk     0
    device          /dev/sdb6
    raid-disk     1

Thanks for any tips,
        Greg

Reply via email to