Ubuntu
dmraid package

Segfault on rebuild

Bug #1221967 reported by Brian Spisak
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
dmraid (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hi,
I have a 4 disk RAID5 array with a failed disk. I removed the bad disk and inserted a new disk. However, when I try to rebuild with the new disk, dmraid crashes. (See details below.)

I read elsewhere that ntfs may cause problems? I have two ntfs partitions. Can this be part of the problem? I need to rebuild my array before I loose another disk! (Of course, I'm backed up.... but still..... :-)

Thanks for any help!

# dmraid -f isw -R isw_chifcdfhf /dev/sdc
ERROR: isw: wrong number of devices in RAID set "isw_chifcdfhf_RAID5" [3/4] on /dev/sdd
ERROR: isw: wrong number of devices in RAID set "isw_chifcdfhf_RAID5" [3/4] on /dev/sde
ERROR: isw: wrong number of devices in RAID set "isw_chifcdfhf_RAID5" [3/4] on /dev/sdf
Segmentation fault (core dumped)

# dmraid -r
*** Group superset isw_chifcdfhf
--> *Inconsistent* Active Subset
name : isw_chifcdfhf_RAID5
size : 3907041280
stride : 256
type : raid5_la
status : inconsistent
subsets: 0
devs : 3
spares : 0

# dmraid -s
/dev/sdf: isw, "isw_chifcdfhf", GROUP, ok, 1953525166 sectors, data@ 0
/dev/sde: isw, "isw_chifcdfhf", GROUP, ok, 1953525166 sectors, data@ 0
/dev/sdd: isw, "isw_chifcdfhf", GROUP, ok, 1953525166 sectors, data@ 0

# # df -T | grep mapper
/dev/mapper/isw_chifcdfhf_RAID5p5 fuseblk 2804317180 884804828 1919512352 32% /mnt/data
/dev/mapper/isw_chifcdfhf_RAID5p2 fuseblk 10485752 4082644 6403108 39% /mnt/share
/dev/mapper/isw_chifcdfhf_RAID5p3 ext4 10321208 3007356 6789564 31% /var
/dev/mapper/isw_chifcdfhf_RAID5p4 ext4 103212320 75764656 22204784 78% /home

# lsb_release -rd
Description: Ubuntu 12.04.2 LTS
Release: 12.04

# apt-cache policy dmraid
dmraid:
  Installed: 1.0.0.rc16-4.1ubuntu8
  Candidate: 1.0.0.rc16-4.1ubuntu8

Revision history for this message
Cedric Kimaru (la6nchpad) wrote :
Download full text (3.7 KiB)

seeing this as well on 12.04

root@amilet:/home/myubuntu# dmraid -R isw_bffghfhhej_RAID5_3Disks /dev/sdc
ERROR: isw: wrong number of devices in RAID set "isw_bffghfhhej_RAID5_3Disks" [2/3] on /dev/sdd
ERROR: isw: wrong number of devices in RAID set "isw_bffghfhhej_RAID5_3Disks" [2/3] on /dev/sdb
Segmentation fault (core dumped)

root@amilet:/home/myubuntu# dmesg
[ 692.512042] show_signal_msg: 48 callbacks suppressed
[ 692.512047] dmraid[3909]: segfault at 0 ip b775ecc9 sp bfdfe720 error 4 in libdmraid.so.1.0.0.rc16[b7747000+35000]

root@amilet:/home/myubuntu# lsb_release -rd
Description: Ubuntu 12.04.3 LTS
Release: 12.04

However, adding debug and verbose doesn't result in the core but raid still doesn't rebuild ;(

root@amilet:/home/myubuntu# dmraid -d -v -R isw_bffghfhhej_RAID5_3Disks /dev/sdc
DEBUG: not isw at 721419264
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 720337408
DEBUG: not isw at -1024
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at -1082880
DEBUG: not isw at -1024
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at -1082880
DEBUG: not isw at -2105541632
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at -2106623488
DEBUG: not isw at -1055826944
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at -1056908800
DEBUG: not isw at -1055826944
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at -1056908800
DEBUG: not isw at -1055826944
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at -1056908800
DEBUG: not isw at -1055826944
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at -1056908800
DEBUG: not isw at -1055826944
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at -1056908800
DEBUG: not isw at -1055826944
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at -1056908800
DEBUG: not isw at -522494976
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at -523576832
DEBUG: not isw at -522494976
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at -523576832
DEBUG: not isw at -1055826944
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at -1056908800
DEBUG: isw metadata found at -522494976 from probe at 232

DEBUG: not isw at -522494976
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at -523576832
DEBUG: isw metadata found at -522494976 from probe at 232

DEBUG: not isw at 1891654656
DEBUG: isw trying hard coded -2115 offset.
DEBUG: not isw at 1890572800
DEBUG: _find_set: searching /dev/sdc
DEBUG: _find_set: not found /dev/sdc
DEBUG: _find_set: searching isw_bffghfhhej
DEBUG: _find_set: not found isw_bffghfhhej
DEBUG: _find_set: searching isw_bffghfhhej_RAID5_3Disks
DEBUG: _find_set: searching isw_bffghfhhej_RAID5_3Disks
DEBUG: _find_set: not found isw_bffghfhhej_RAID5_3Disks
DEBUG: _find_set: not found isw_bffghfhhej_RAID5_3Disks
DEBUG: freeing devices of RAID set "isw_bffghfhhej_RAID5_3Disks"
DEBUG: freeing device "isw_bffghfhhej_RAID5_3Disks", path "/dev/sdd"
DEBUG: freeing devices of RAID set "isw_bffghfhhej"
DEBUG: freeing device "isw_bffghfhhej", path "/dev/sdd"
DEBUG: _find_set: searching isw_bffghfhhej
DEBUG: _...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in dmraid (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Related questions

Remote bug watches

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