Crash "No Such File Or Directory"

[Nick]

Binary package hint: sbackup

I backed up my home directory with Ubuntu 7.10 to a NAS. I just installed (03/29/2008) Ubuntu 8.04 Beta. Sbackup crashes EVERY SINGLE TIME I try to restore a directory from my NAS.

I am attempting to restore the directory /home/nhilton/development.

Here is the traceback:

PythonArgs: ['/usr/sbin/simple-restore-gnome']
Traceback:
 Traceback (most recent call last):
   File "/usr/sbin/simple-restore-gnome", line 409, in restore
     self._do_restore( self.src, self.src )
   File "/usr/sbin/simple-restore-gnome", line 402, in _do_restore
     r.restore( tdir, src, dst )
   File "/usr/share/sbackup/srestore.py", line 112, in restore
     shutil.move( os.path.join(tdir,spath), dpath )
   File "/usr/lib/python2.5/shutil.py", line 199, in move
     copy2(src,dst)
   File "/usr/lib/python2.5/shutil.py", line 91, in copy2
     copyfile(src, dst)
   File "/usr/lib/python2.5/shutil.py", line 46, in copyfile
     fsrc = open(src, 'rb')
 IOError: [Errno 2] No such file or directory: '/home/nhilton/tmpnEQjrg/home/nhilton/development'

After the crash, the temp dir "/home/nhilton/tmpnEQjrg" exists but is empty.

This is critical, I can not restore any files!

[Nick (weegreenblobbie)]

This is NOT a bug, it turns out that the created archive was corrupt.

Manually trying to extract the archive gave me a "unexpected end of file" on the files.tgz that sbackup made. Looking closer at it's size, files.tgz was exactly 2147483647, 1 byte short of 2GB. I bet this failure occurs when the archive is not extracted and there are no files to copy to the proper location.

So perhaps the real bug is that sbackup is unable to create tgz files larger that 2GB?

Maybe I didn't notice my backup failed on Ubuntu 7.10 when I created it. sbackup did successfully create an incremental backup using the "full" backup. I bet sbackup doesn't even check files.tgz when doing an incremental, but just checks what file versions have changed by looking at flist or something.

So, the real bug is that sbackup is unable to create tgz files larger that 2GB!

[Nick (weegreenblobbie)]

I just realized that my nas is sharing it's volume over samba, it may only support a max filesize of 2GB.

[Nick (weegreenblobbie)]

Mounting my NAS using cifs instead of cifs seems to have worked.

[Nick (weegreenblobbie)]

Mounting my NAS using CIFS instead of SMBFS seems to have worked.

[Oumar Aziz OUATTARA (wattazoum)]

Thank you for your bug report.

After your comments, I believe I can safely put this bug as invalid. right ? just tell me if I should reopen it .

Regards

[Nick (weegreenblobbie)]

Perhaps the correct action would be to add some checking that the backup was created successfully. I didn't get a notification that the backup failed.

Oumar Aziz OUATTARA <email address hidden> wrote: Thank you for your bug report.

After your comments, I believe I can safely put this bug as invalid.
right ? just tell me if I should reopen it .

Regards

** Changed in: sbackup (Ubuntu)
     Assignee: (unassigned) => Oumar Aziz OUATTARA (wattazoum)
       Status: New => Invalid

--
Crash "No Such File Or Directory"
https://bugs.launchpad.net/bugs/209314
You received this bug notification because you are a direct subscriber
of the bug.

---------------------------------
OMG, Sweet deal for Yahoo! users/friends: Get A Month of Blockbuster Total Access, No Cost. W00t

[Eivind Ødegård (eivind)]

I suggest reopening this bug. Yesterday, I posted a question about the same error:

https://answers.launchpad.net/ubuntu/+source/sbackup/+question/30719

I have backed up to an external USB drive (an Iaudio X5 really) directly connected to my laptop. The symptoms (creation of empty temporary directories when trying to restore etc.) and error messages are similar - everything below

File "/usr/share/sbackup/srestore.py", line 112

is identical in both cases. I too regard this bug as quite critical.

[Eivind Ødegård (eivind)]

Reopening because of identical tracebacks under different circumstances than described in the original bug.

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 or 9.04?

[Neil Perry (nperry)]

This bug is still marked as Incomplete so we are now going to close this bug report. Please upgrade to the latest release Karmic 9.10 - If this bug is still reproducible please reopen the bug by setting the status to New. Thanks