mdadm crashed with SIGSEGV in __libc_start_main()

Bug #347747 reported by Steve Beattie
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mdadm (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: mdadm

This bug report is intended to capture a backtrace for bug 316670, which it will be a duplicate of.

Steps to recreate:
1) create 4 empty loopback disks:

  for i in $(seq 1 4) ; do
      dd if=/dev/zero of=disk${i} bs=1024 count=512000
      sudo losetup /dev/loop${i} disk${i}
  done

2) create raid10 array

  sudo mdadm -C /dev/md0 -l raid10 -n 4 /dev/loop{1,2,3,4}

3) stop the array:

  sudo mdadm --stop /dev/md0

4) incrementally assemble the first loop device

  sudo mdadm --incremental /dev/loop1

et voila, segv.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /sbin/mdadm
Package: mdadm 2.6.7.1-1ubuntu7
ProcAttrCurrent: unconfined
ProcCmdline: mdadm --incremental /dev/loop1
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_IN.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: mdadm
Stacktrace:
 #0 0x0804fe08 in ?? ()
 #1 0x080602f6 in ?? ()
 #2 0x0804cc9c in ?? ()
 #3 0xb7dbd775 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #4 0x08049c31 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Title: mdadm crashed with SIGSEGV in __libc_start_main()
Uname: Linux 2.6.28-11-generic i686
UserGroups:

Revision history for this message
Steve Beattie (sbeattie) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:enough (level=10, raid_disks=4, layout=258, clean=1, avail=0x0,
Incremental (devname=0xbf938a5f "/dev/loop1", verbose=0,
main (argc=3, argv=0xbf9372f4) at mdadm.c:1373

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in mdadm:
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.