Hallo Neil!
"NeilBrown" <neilb@xxxxxxx> schrieb:
> On Sat, May 24, 2008 1:00 am, Lars Täuber wrote:
> > Sorry!
> >
> >> mdadm version 2.6.6 although it is reported as:
> >> monosan:~ # mdadm -V
> >> mdadm - v2.6 - 21 December 2006
> >
> > I accidentally compiled mdadm 2.6 instead of 2.6.6. But this is even
> > worse:
> >
> > monosan:~ # mdadm -V
> > mdadm - v2.6.6 - 19th May 2008
> > monosan:~ # mdadm -As
> > Segmentation fault
>
> That's bad.
> What do you get from:
>
> ulimit -c unlimited
> mdadm -As
> gdb `which mdadm` core
> where
>
monosan:~ # ulimit -c unlimited
monosan:~ # mdadm -As
Speicherzugriffsfehler (core dumped)
monosan:~ # gdb `which mdadm` core
GNU gdb 6.6.50.20070726-cvs
Copyright (C) 2007 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-suse-linux"...
Using host libthread_db library "/lib64/libthread_db.so.1".
warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib64/libc.so.6...done.
Loaded symbols for /lib64/libc.so.6
Reading symbols from /lib64/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Core was generated by `mdadm -As'.
Program terminated with signal 11, Segmentation fault.
#0 0x000000000040cd72 in Assemble (st=0x0, mddev=0x6364f0 "/dev/md4", mdfd=3,
ident=0x636630, devlist=0x636b90, backup_file=0x0, readonly=0, runstop=0,
update=0x0, homehost=0x0, verbose=0, force=0) at Assemble.c:370
370 tst->ss->free_super(tst);
(gdb) where
#0 0x000000000040cd72 in Assemble (st=0x0, mddev=0x6364f0 "/dev/md4", mdfd=3,
ident=0x636630, devlist=0x636b90, backup_file=0x0, readonly=0, runstop=0,
update=0x0, homehost=0x0, verbose=0, force=0) at Assemble.c:370
#1 0x00000000004058a4 in main (argc=2, argv=0x7fff2317c6d8) at mdadm.c:1086
(gdb)
I hope this helps.
Any idea on the actual subject?
Lars
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
