← Back to team overview

nssbackup-team team mailing list archive

[Bug 666500] [NEW] Sbackup doesn't check for full remote disk

 

Public bug reported:

Binary package hint: sbackup

I've been running sbackup for a while, backing up to a remote drive over
sftp and using logarithmic purging. However, periodically backups start
crashing with confusing error messages (I don't recall what they said
exactly). When these crashes occur, when I test the destination with
sbackup-config-gtk it tells me that the remote destination was
unavailable for an "unknown reason". When I check my remote drive, it is
completely filled with backups. Removing some backups will allow sbackup
to start working again, but only temporarily.

Ideally, sbackup would notice that I had filled my drive and remove some
old backups, instead of failing mysteriously.

$ lsb_release -rd
Description:	Ubuntu 10.10
Release:	10.10

$ apt-cache policy sbackup
sbackup:
  Installed: 0.11.3ubuntu1
  Candidate: 0.11.3ubuntu1
  Version table:
 *** 0.11.3ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ maverick/universe i386 Packages
        100 /var/lib/dpkg/status

** Affects: sbackup (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  Binary package hint: sbackup
  
  I've been running sbackup for a while, backing up to a remote drive over
  sftp and using logarithmic puring. However, periodically backups start
  crashing with confusing error messages. When these crashes occur, when I
  test the destination with sbackup-config-gtk it tells me that the remote
  destination was unavailable for an "unknown reason". When I check my
  remote drive, it is completely filled with backups. Removing some
  backups will allow sbackup to start working again, but only temporarily.
  
  Ideally, sbackup would notice that I had filled my drive and remove some
  old backups, instead of failing mysteriously.
  
  $ lsb_release -rd
  Description:	Ubuntu 10.10
  Release:	10.10
  
  $ apt-cache policy sbackup
  sbackup:
-   Installed: 0.11.3ubuntu1
-   Candidate: 0.11.3ubuntu1
-   Version table:
-  *** 0.11.3ubuntu1 0
-         500 http://us.archive.ubuntu.com/ubuntu/ maverick/universe i386 Packages
-         100 /var/lib/dpkg/status
+   Installed: 0.11.3ubuntu1
+   Candidate: 0.11.3ubuntu1
+   Version table:
+  *** 0.11.3ubuntu1 0
+         500 http://us.archive.ubuntu.com/ubuntu/ maverick/universe i386 Packages
+         100 /var/lib/dpkg/status

** Description changed:

  Binary package hint: sbackup
  
  I've been running sbackup for a while, backing up to a remote drive over
- sftp and using logarithmic puring. However, periodically backups start
- crashing with confusing error messages. When these crashes occur, when I
- test the destination with sbackup-config-gtk it tells me that the remote
- destination was unavailable for an "unknown reason". When I check my
- remote drive, it is completely filled with backups. Removing some
- backups will allow sbackup to start working again, but only temporarily.
+ sftp and using logarithmic purging. However, periodically backups start
+ crashing with confusing error messages (I don't recall what they said
+ exactly). When these crashes occur, when I test the destination with
+ sbackup-config-gtk it tells me that the remote destination was
+ unavailable for an "unknown reason". When I check my remote drive, it is
+ completely filled with backups. Removing some backups will allow sbackup
+ to start working again, but only temporarily.
  
  Ideally, sbackup would notice that I had filled my drive and remove some
  old backups, instead of failing mysteriously.
  
  $ lsb_release -rd
  Description:	Ubuntu 10.10
  Release:	10.10
  
  $ apt-cache policy sbackup
  sbackup:
    Installed: 0.11.3ubuntu1
    Candidate: 0.11.3ubuntu1
    Version table:
   *** 0.11.3ubuntu1 0
          500 http://us.archive.ubuntu.com/ubuntu/ maverick/universe i386 Packages
          100 /var/lib/dpkg/status

-- 
Sbackup doesn't check for full remote disk
https://bugs.launchpad.net/bugs/666500
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup in ubuntu.



Follow ups

References