Backup restore crashed while restoring

Bug #300489 reported by amarradi
2
Affects Status Importance Assigned to Milestone
sbackup
Status tracked in Trunk
0.10
Fix Committed
Medium
Unassigned
Trunk
Invalid
Undecided
Unassigned

Bug Description

Hello together,

i'm using sbackup 0.10.5 under intrepid. So i have one fullbackup with 15 GB and 7 incremential backups with 70~100 MB.
Yesterday i tryed to restore my AdressDB(26 KB). It worked, but the sbackup crased, with no reaction.

I'm using an Harddisk 60 GB with the XFS Filesystem... No Window reaction or error messages. The file is restored sucessfully. But The Software crashed.

Many greetings

Marcus Radisch

Revision history for this message
Martin Schaaf (mascha) wrote :

Please can you start the restore process from a terminal, let it crash and attach the output. Thank you for your help.

Changed in sbackup:
status: New → Incomplete
Revision history for this message
amarradi (forum-marcusradisch) wrote :

Hello Martin,

how do i get an error output, the onle output is by choosing the restore-path
error1.txt
But no output after i killed the simple backup because it runs and runs andd runs. After 5 minutes the Application said "The application stops responding" Force Quit or waiting i choosed the first. The location where i restored the File from the fulbackup is a new folder tmpi2u-Qi with sudo rights. If i opend it with sudo rights i find my file. And the File is OK

Many greetings

Marcus Radisch

Revision history for this message
Martin Schaaf (mascha) wrote :

I reproduced your "crash", but it is no crash. There are two problems here. First the python threading in gtk isn't enabled. This leads to a blocking UI and this looks for the user as a crashing or hanging application. The second problem is the tar it is started with the occurrence parameter to stop after extracting all files but it doesn't. It waits until gzip has extracted the complete backup tar. I start working on a fix by enabling gtk threading and showning the user that there is progress.

Changed in sbackup:
assignee: nobody → mascha
importance: Undecided → Medium
status: Incomplete → Confirmed
Revision history for this message
Martin Schaaf (mascha) wrote :

> The second problem is the tar it is started with the occurrence parameter to stop after extracting all files but it doesn't.

This is a bug in gnu tar.

Revision history for this message
amarradi (forum-marcusradisch) wrote :

Hello Martin,

Do you open the ticket for this Bug for tar. or should i do it? You know what the Error is, you should do it.

many greetings

Marcus Radisch

Revision history for this message
Martin Schaaf (mascha) wrote :

I asked on there ML and they responded with a patch so I thing a bug in gnu tar isn't necessary, but possbily one for tar ubuntu. I will do this.

Revision history for this message
Martin Schaaf (mascha) wrote :

Fix is in this branch https://code.edge.launchpad.net/~mascha/sbackup/0.10.5_with_fixes since revision 26. Current tar version in ubuntu is 1.22 which includes the fix for not respecting the occurrence parameter.

Changed in sbackup:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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