Opened 12 years ago

Closed 12 years ago

#199 closed defect (fixed)

mondoarchive fails on fedora core 6 with segfault or hangs with SIGABRT

Reported by: tadej Owned by: bruno
Priority: normal Milestone: 2.2.5
Component: mondo Version: 2.2.4
Severity: normal Keywords:
Cc:

Description

Hi!

I'm using mondorescue on Fedora core 6:

mondo-2.2.4-1.fc6
mindi-1.2.4-1.fc6
mindi-busybox-1.2.2-3.fc6
kernel-2.6.20-1.2952.fc6
kernel-2.6.22.7-57.fc6

I've booted the system to runlevel 3 and tried to backup the system to external USB hard disk:

mondoarchive -O -i -d /mnt/wdext/backup/ -p tlinux-stable -N -E "/mnt/wdext" -S /mnt/wdext/backup/scratch/ -F -z -s 4480m

After a few hours, mondorescue exited with error message:

Segmentation fault

The log file doesn't indicate anything unusual. If you want, I can recompile mondoarchive with debugging symbols and run it with valgrind.

I've been trying to backup this machine for a week now with no success. I've tried backing it up to a CIFS mounted Windows share, i've changed .iso size from 4480m to 700m, I've updated the kernel to version 2.6.22.7, but mondoarchive never successfully finished. It either terminated with a segmentation fault or kernel threw some strange symbols to the screen followed by message:

SIGABRT signal received from OS

I'll also attach the second log file with SIGABORT issue.

Do you have any clue, what is the culprit here?

I've searched for similar trac tickets and the best "match" was Ticket #97, however, it is supposed to be fixed by now. My newt and fribidi packages are the following:

newt-0.52.2-9
fribidi-0.10.7-5.1

Thank you for your response!

Attachments (3)

mondoarchive.log (453.0 KB) - added by tadej 12 years ago.
Log file of mondoarchive failing with Segmentation fault
mondoarchive2.log (701.8 KB) - added by tadej 12 years ago.
Mondoarchive failing with SIGABRT signal received from OS
mondoarchive3.log (254.9 KB) - added by tadej 12 years ago.
Mondoarchive failing in gdbc

Download all attachments as: .zip

Change History (7)

Changed 12 years ago by tadej

Log file of mondoarchive failing with Segmentation fault

Changed 12 years ago by tadej

Mondoarchive failing with SIGABRT signal received from OS

comment:1 Changed 12 years ago by tadej

I recompiled mondo-2.2.4 from source as described in TroubleShooting page of the wiki. Then I ran mondoarchive via gdb (this time without the -z option) and mondo still crashed, however, I wasn't able to obtain the backtrace:

(trimmed)
---evalcall---1---    Running mkisofs to make ISO #1
---evalcall---2--- TASK:  [********************]  99% done;  0:06 to go
---evalcall---E---
[Thread -1230042224 (LWP 27637) exited]
Call to mkisofs to make ISO (ISO #1) ...OK
Couldn't get registers: No such process.
(gdb) bt
Couldn't get registers: No such process.
(gdb)

I'll attach the mondoarchive.log file as mondoarchive3.log

Changed 12 years ago by tadej

Mondoarchive failing in gdbc

comment:2 Changed 12 years ago by bruno

  • Status changed from new to assigned

I've made a pre version of 2.2.5 available at ftp://ftp.mondorescue.org/fedora/6 Could you try to use it to check whether this was fixed in between or if it's still there.

If it's still there, then I'd appreciate if you could run it with valgrind in order to get a better idea of where it's aborting.

TIA

comment:3 Changed 12 years ago by tadej

I'm back!

I was quite pleasantly surprised with mondo-2.2.5. In the last 2 days, I made 2 successful backups to external USB hard disk. FWIW, this is no longer an issue for me :)

Thank you, Bruno!

comment:4 Changed 12 years ago by bruno

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.