nssbackup-team team mailing list archive

[Jim Kirkpatrick <bad.octopus@xxxxxxxxx>]

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/22887427/Dependencies.txt

** Attachment added: "ProcMaps.txt"
   http://launchpadlibrarian.net/22887428/ProcMaps.txt

** Attachment added: "ProcStatus.txt"
   http://launchpadlibrarian.net/22887429/ProcStatus.txt

** Attachment added: "Traceback.txt"
   http://launchpadlibrarian.net/22887430/Traceback.txt

** Visibility changed to: Public

** Description changed:

  Binary package hint: sbackup
  
  Ran a backup, went away for a while whilst it worked, came back and it
  had crashed.
  
- Had 3.6Gb free on destination drive and but the disk was full when I
- returned. Am guessing it failed because of this.
+ Had 3.6Gb free on destination drive at start but the disk was completely
+ full when I returned. Am guessing it crashed because of this.
  
  Availability of free space is obviously a key requirement of sbackup, so
- it seems like a bug that a crash happens if destination becomes full. A
- user message and syslog entry would be much more appropriate.
+ it is a bug that a crash happens if destination becomes full. A user
+ message and syslog entry would be much more appropriate.
  
  ProblemType: Crash
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/share/sbackup/sbackupd.py
  InterpreterPath: /usr/bin/python2.5
  NonfreeKernelModules: fglrx
  Package: sbackup 0.10.5ubuntu2
  PackageArchitecture: all
  ProcAttrCurrent: unconfined
  ProcCmdline: /usr/bin/python /usr/sbin/sbackupd
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/sbin/sbackupd']
  SourcePackage: sbackup
  Title: sbackupd.py crashed with IOError in copyfileobj()
  Uname: Linux 2.6.27-11-generic i686
  UserGroups:

** Description changed:

  Binary package hint: sbackup
  
  Ran a backup, went away for a while whilst it worked, came back and it
  had crashed.
  
- Had 3.6Gb free on destination drive at start but the disk was completely
- full when I returned. Am guessing it crashed because of this.
+ Had 3.6Gb free on destination drive (FAT32) at start but the disk was
+ completely full when I returned. Am guessing it crashed because of this.
  
  Availability of free space is obviously a key requirement of sbackup, so
  it is a bug that a crash happens if destination becomes full. A user
  message and syslog entry would be much more appropriate.
  
  ProblemType: Crash
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/share/sbackup/sbackupd.py
  InterpreterPath: /usr/bin/python2.5
  NonfreeKernelModules: fglrx
  Package: sbackup 0.10.5ubuntu2
  PackageArchitecture: all
  ProcAttrCurrent: unconfined
  ProcCmdline: /usr/bin/python /usr/sbin/sbackupd
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/sbin/sbackupd']
  SourcePackage: sbackup
  Title: sbackupd.py crashed with IOError in copyfileobj()
  Uname: Linux 2.6.27-11-generic i686
  UserGroups:

-- 
sbackupd.py crashed with IOError in copyfileobj()
https://bugs.launchpad.net/bugs/331778
You received this bug notification because you are a member of NSsbackup
team, which is subscribed to sbackup in ubuntu.