Share

recover

Tracker: Bugs

5 Repeatable segfault during initial inode scan - ID: 662360
Last Update: Comment added ( nok )

Hello,

another bugreport:

http://bugs.debian.org/156102

"recover segfaults during the inode scan. gdb session
with backtrace
follows:

# gdb recover
[snip gdb startup messages]
(gdb) run /dev/md1
Starting program: /usr/bin/recover /dev/md1
Recover v1.3b by Tom Pycke <Tom.Pycke@advalvas.be>

Getting inodes (this can take some time)...
debugfs 1.27 (8-Mar-2002)
(no debugging symbols found)...(no debugging symbols
found)...
Program received signal SIGSEGV, Segmentation fault.
0x08048efd in strcpy ()
(gdb) backtrace
#0 0x08048efd in strcpy ()
#1 0x0804c390 in ?? ()
#2 0x08049b42 in strcpy ()
#3 0x080494f6 in strcpy ()
#4 0x4003514f in __libc_start_main () from /lib/libc.so.6
(gdb)

I wish this were more helpful; if you think it woould
help I'll rebuild
from source with debugging symbols and test again.

This is a 15 GB RAID-5 array, but it should still work,
right? Also,
we're using the pre-packaged Debian 686-smp kernel.

Thank you,"


Noèl Köthe ( nok ) - 2003-01-04 22:05

5

Closed

Fixed

Nobody/Anonymous

None

None

Public


Comment ( 1 )




Date: 2003-02-22 11:56
Sender: nok

Logged In: YES
user_id=208203

fixed in 1.3c


Log in to comment.

Attached File

No Files Currently Attached

Changes ( 3 )

Field Old Value Date By
status_id Open 2003-02-22 11:56 nok
resolution_id None 2003-02-22 11:56 nok
close_date - 2003-02-22 11:56 nok