On Sat, 09 Apr 2011 10:09:49 +0200 Arnaud Desmier
wrote:
> Is it interesting?
Unfortunately not - or not very.
Could you please:
Add "-vv" to the mdadm option and run again and collect the output.
run mdadm under 'strace'. i.e.
strace -o /tmp/trace mdadm --assemble
and send th
It seems that "mdadm --assemble --scan --auto=yes --symlink=no" is the
faulty invocation.
I've run gdb using package mdadm but it couldn't find any debug
symbol... So I run the following command as Makefile displays when
compiling package:
gcc -o mdadm mdadm.o config.o mdstat.o ReadMe.o util
also sprach Arnaud Desmier [2011.04.09.0923
+0200]:
> How can I get the stack trace as you requested?
Find the exact invocation of mdadm that produces the problem and run
it under gdb until it crashes. The stacktrace you can then get with
'bt'.
--
.''`. martin f. krafft Related projec
Hi Martin,
I've made the following changes before compiling the debian package
version (not the one build from git repository):
debian/rules:
- change declaration of CXFLAGS to CXFLAGS = -ggdb -DDEBUG -g
Before building package:
- export DEB_BUILD_OPTIONS="noopt"
Starting build of package:
tags 621786 moreinfo
thanks
> /etc/init.d/mdadm-raid restart
> *** glibc detected *** /sbin/mdadm: munmap_chunk(): invalid pointer:
> 0x00084800 ***
> *** glibc detected *** /sbin/mdadm: malloc(): memory corruption: 0x00084660
> ***
> Aborted
Please compile mdadm with debug symbols and get a st
Package: mdadm
Version: 3.1.4.1-0
Severity: critical
Justification: breaks the whole system
One month ago I tried to install Debian Squeeze on my QNAP TS-409 nas (see
configuration bellow). During the installation process I saw an error message
like "invalid pointer" or "memory corruption", but
6 matches
Mail list logo
