Have you tried the latest version, 0.6.13?  Some of the problems you are
encountering are fixed in that version.

...Ken

On Sat, Jun 11, 2011 at 10:54 AM, Kenneth Loafman <email address hidden>wrote:

> I'll look into this over the weekend.
>
> The error counter is per write, not overall.  There really should be an
> overall error count just to document how many errors occurred.
>
>
> On Sat, Jun 11, 2011 at 10:26 AM, Michael Rodríguez-Torrent <
> <email address hidden>> wrote:
>
>> Had a look at giobackend.py, and I guess the error came up because the
>> exception handler expects the iterator counter n to be in scope, but
>> it's not. The bigger problem, however, is that the exception occurred --
>> which I suppose has to mean that the write failed multiple times.
>>
>> Any idea why it would at this point? The backup had been running for
>> somewhere approaching 18 hours by then without problem. Is the retry
>> cumulative across the entire execution or is it per write?
>>
>> --
>> You received this bug notification because you are subscribed to
>> Duplicity.
>> https://bugs.launchpad.net/bugs/545486
>>
>> Title:
>>  Backup fails with 'Error: No data available'
>>
>> Status in Déjà Dup Backup Tool:
>>  In Progress
>> Status in Duplicity - Bandwidth Efficient Encrypted Backup:
>>  New
>>
>> Bug description:
>>  When attempting to run a backup of my home directory to a network
>>  mount, Deja Dup eventually reports that the backup has failed with
>>  "Error: Invalid argument."
>>
>>  I'm running Ubuntu 9.10
>>
>>  I have tried this on both the current stable release (11.1) and the
>>  current edge release (13.92).
>>
>>  Duplicity version is 0.6.08-0ubuntu0karmic1
>>
>>  gconf is attached
>>
>>  The end of the debug log follows:
>>
>>  DUPLICITY: INFO 2 90202160095
>>
>>  DUPLICITY: WARNING 10 '/lost+found'
>>  DUPLICITY: . Error accessing possibly locked file /lost+found
>>
>>  DUPLICITY: WARNING 10 '/root'
>>  DUPLICITY: . Error accessing possibly locked file /root
>>
>>  DUPLICITY: INFO 2 90202160095
>>
>>  DUPLICITY: DEBUG 1
>>  DUPLICITY: . Removing still remembered temporary file
>> /tmp/duplicity-CVEgG8-tempdir/mkstemp-J9KUEY-1
>>
>>  DUPLICITY: ERROR 30 Error
>>  DUPLICITY: . Traceback (most recent call last):
>>  DUPLICITY: .   File "/usr/bin/duplicity", line 1239, in <module>
>>  DUPLICITY: .     with_tempdir(main)
>>  DUPLICITY: .   File "/usr/bin/duplicity", line 1232, in with_tempdir
>>  DUPLICITY: .     fn()
>>  DUPLICITY: .   File "/usr/bin/duplicity", line 1210, in main
>>  DUPLICITY: .     full_backup(col_stats)
>>  DUPLICITY: .   File "/usr/bin/duplicity", line 408, in full_backup
>>  DUPLICITY: .     col_stats.set_values(sig_chain_warning=None)
>>  DUPLICITY: .   File
>> "/usr/lib/python2.6/dist-packages/duplicity/collections.py", line 658, in
>> set_values
>>  DUPLICITY: .     backend_filename_list = self.backend.list()
>>  DUPLICITY: .   File
>> "/usr/lib/python2.6/dist-packages/duplicity/backends/giobackend.py", line
>> 127, in list
>>  DUPLICITY: .     gio.FILE_QUERY_INFO_NOFOLLOW_SYMLINKS)
>>  DUPLICITY: . Error: Invalid argument
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/deja-dup/+bug/545486/+subscriptions
>>
>
>