simple-restore-gnome.py crashed with OSError in cmp()

Bug #231841 reported by Bart Samwel
28
This bug affects 2 people
Affects Status Importance Assigned to Milestone
sbackup (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: sbackup

I had a restore running overnight (12 GB full backup over a wireless 54 Mb/s connection), and my wireless died somewhere during the night. When I got back in the morning, I got this crash report. Apparently it's not so resilient against network failures.

ProblemType: Crash
Architecture: amd64
Date: Mon May 19 00:28:15 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/share/sbackup/simple-restore-gnome.py
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: nvidia
Package: sbackup 0.10.4
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/simple-restore-gnome
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/sbin/simple-restore-gnome']
SourcePackage: sbackup
Title: simple-restore-gnome.py crashed with OSError in cmp()
Uname: Linux 2.6.24-16-generic x86_64
UserGroups:

Tags: apport-crash
Revision history for this message
Bart Samwel (bart-samwel) wrote :
Revision history for this message
Ron B. (flybye882001) wrote :

I am not sure if this is the right bug report to sub. to - I dont know enough about linux.
This morning i upgraded from 8.10 to 9.04 beta - and the sound broke. I was trying to restore the /var with a simple restore from data laid down 2 days ago. Have no idea if this can be done accross two ubuntu versions. Had tried all day with help from irc #'s etc to fix the stuff with no success before this desparate attempt.

Revision history for this message
Glen (gtlxiii) wrote :

The primary backup unit is an external USB 2.0 HDD (IDE 5.25). It also crashes with same error from the backup files copied to the internal HDD. (ie. \home\glen\downloads\backup)

Revision history for this message
Glen (gtlxiii) wrote :

I identified the problem as being a corrupt tar file. File too large for external file system.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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