IOError on incremental backup

[emilio]

I am running
deja-dup 10.1-0jaunty1
duplicity 0.6.05-0jaunty1

During an incremental backup duplicity fails with IOError

The log is attached

[Michael Terry (mterry)]

This seems odd. Looks like maybe the directory it was trying to write to [1] wasn't writable? It was able to read other files in that directory, but by the time it wants to write something there, an IOError is given. I assume you can manually create files on the share fine?

[1] /home/emilio/.gvfs/emiliobackup on mybookworld/e4300_backup/

[emilio (emiliomaggio)]

Yes the share is available for both read and write. Also, I tried to run
deja-dup again and the backup operation was successful.

On Sun, 2009-09-06 at 20:28 +0000, Michael Terry wrote:
> This seems odd. Looks like maybe the directory it was trying to write
> to [1] wasn't writable? It was able to read other files in that
> directory, but by the time it wants to write something there, an IOError
> is given. I assume you can manually create files on the share fine?
>
> [1] /home/emilio/.gvfs/emiliobackup on mybookworld/e4300_backup/
>

[Kenneth Loafman (kenneth-loafman)]

This sounds like a transient error to me. Were you running to the file:// protocol using GVFS? If so, switch to one of the error retrying protocols such as SSH and try that. The file:// protocol is for local disks and mounts that have their own built in error handling.

[Michael Terry (mterry)]

I'll note that using Deja Dup, you can't switch protocols like Ken suggested, emilio. That's only if you used duplicity's command line directly.

If Deja Dup's working for you now, I'd say ignore it. Deja Dup 11.0 will use duplicity's gio backend, which should make issues like this go away. (/me crosses fingers)

[Michael Terry (mterry)]

Marking fix committed from Deja Dup's side, since in 11.0, we'll use gio backend and transient errors due to the FUSE layer (which is what this sounds like) should go away.