NeilBrown wrote:
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
??
NeilBrown
I saw this last week, but can unfortunately only offer limited
information - for various reasons, this system is no longer available.
On an up to date Fedora 8 x86_64 2.6.24.7-92.fc8 sytem, I replaced mdadm
with a locally built mdadm 2.6.5 - compiled with -O2.
On the next reboot, the md RAID1 / failed to assemble, with mdadm
errors. When I accessed from a rescue disk, running mdadm -A /dev/mdX
(can't rember exact dev), returned "Segmentation fault".
If it's any use, I do still have a complete mdadm 2.6.5 tree containing
the faulty objects from this system.
Regards,
Richard
--
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
