On Thu, Oct 28, 2010 at 1:03 AM, Jerry Amundson <jamundso(a)gmail.com> wrote:
On Sat, Oct 23, 2010 at 11:50 AM, M A Young
<m.a.young(a)durham.ac.uk> wrote:
> Try xen kernel-2.6.32.25-171.rc1.xendom0.fc12 instead at
>
http://koji.fedoraproject.org/koji/taskinfo?taskID=2550132 or at the
> repository
http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ which has
> a fix for that and another security hole.
Anyone else seeing problems with software raid?
On a new Fedora 14 system, the distro kernel is fine, but my 4 SCSI
drive system has md devices fail with xendom0...
Oct 27 23:31:17 elm kernel: [ 40.504212] dracut: mdadm: /dev/md0 has
been started with 2 drives.
Oct 27 23:31:17 elm kernel: [ 40.590546] dracut: mdadm: /dev/md1 has
been started with 2 drives.
Oct 27 23:31:17 elm kernel: [ 40.629581] dracut: mdadm: /dev/md2 has
been started with 3 drives.
Oct 27 23:31:17 elm kernel: [ 40.709149] dracut: mdadm: /dev/md3 has
been started with 3 drives.
[snip]
Oct 27 23:39:55 elm kernel: dracut: mdadm: /dev/md0 has been started
with 2 drives.
Oct 27 23:39:55 elm kernel: dracut: mdadm: /dev/md1 has been started
with 2 drives.
Oct 27 23:39:55 elm kernel: mdadm[617]: segfault at 46 ip 006b7997 sp
bfe4b2d0 error 4 in libc-2.12.90.so[658000+18d000]
Oct 27 23:39:55 elm kernel: mdadm[636]: segfault at 46 ip 006b7997 sp
bfa19490 error 4 in libc-2.12.90.so[658000+18d000]
The "Oct 27 23:31:17" messages reflect fc14, while "Oct 27 23:39:55"
is xendom0.
The system boots fine, but just won't see the extra meta devices.
I was tripped up by my own kernel hopping - the current mdadm.conf
wasn't present in the initramfs made with the kernel install done
earlier. A mkinitrd for the needful kernel, and poof! the raid devices
are fine.
jerry