"IOError: [Errno 28] No space left on device" with plenty of space

Bug #1432719 reported by Bastien Nocera
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Déjà Dup
Fix Released
Undecided
Unassigned

Bug Description

deja-dup-32.0-3.fc22.x86_64

The last few lines of the logs:
DUPLICITY: ERROR 30 IOError
DUPLICITY: . Traceback (most recent call last):
DUPLICITY: . File "/usr/bin/duplicity", line 1509, in <module>
DUPLICITY: . with_tempdir(main)
DUPLICITY: . File "/usr/bin/duplicity", line 1503, in with_tempdir
DUPLICITY: . fn()
DUPLICITY: . File "/usr/bin/duplicity", line 1352, in main
DUPLICITY: . do_backup(action)
DUPLICITY: . File "/usr/bin/duplicity", line 1381, in do_backup
DUPLICITY: . sync_archive(decrypt)
DUPLICITY: . File "/usr/bin/duplicity", line 1154, in sync_archive
DUPLICITY: . copy_to_local(fn)
DUPLICITY: . File "/usr/bin/duplicity", line 1099, in copy_to_local
DUPLICITY: . gpg.GzipWriteFile(src_iter, tdp.name, size=sys.maxint)
DUPLICITY: . File "/usr/lib64/python2.7/site-packages/duplicity/gpg.py", line 387, in GzipWriteFile
DUPLICITY: . gzip_file.write(new_block.data)
DUPLICITY: . File "/usr/lib64/python2.7/gzip.py", line 243, in write
DUPLICITY: . self.fileobj.write( self.compress.compress(data) )
DUPLICITY: . File "/usr/lib64/python2.7/site-packages/duplicity/gpg.py", line 369, in write
DUPLICITY: . result = self.fileobj.write(buf)
DUPLICITY: . IOError: [Errno 28] No space left on device

This is probably a duplicate of another bug, but the error message is particularly useless, or even misleading.

Revision history for this message
Bastien Nocera (hadess-deactivatedaccount) wrote :
Revision history for this message
Bastien Nocera (hadess-deactivatedaccount) wrote :

I have 10GB available in /, 4GB in /tmp (in RAM), 5GB in /home and 3.5TB on the NAS which handles backups. I have no idea where there's not enough room...

Michael Terry (mterry)
summary: - Fails with useless error message
+ "IOError: [Errno 28] No space left on device" with plenty of space
Revision history for this message
Michael Terry (mterry) wrote :

This sounds like it was on a NAS, and might have been fixed by changes we made in gvfs/worked-around-in life-deja-dup in mean time. Reopen if you still see this.

Changed in deja-dup:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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