Red Hat Bugzilla – Bug 818821
duplicity fails when running out of disk
Last modified: 2014-04-10 21:52:42 EDT
The backup target has run out of disk space, which is making duplicity fail with "Unknown error". This is rather surprising given that the configuration GUI says "Old backups will be kept for at least six months or until the backup location is low on space.".
Sorry, the message is of course from Deja Dup. I'm not sure who is supposed to handle running out of disk though, so feel free to move it if you feel that this is not a duplicity bug.
Note that running duplicity directly results in a Python traceback due to running out of space, but the process does not exit. I think that's most likely the cause of the problem. Duplicity should handle out-of-space errors by exiting with an appropriate exit code.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Can anyone check with the current release please? Thanks
Closing. If anyone can reproduce this, please reopen