Comment 18 for bug 487720

This is exactly what I'm seeing in bug 491971. The transfer is interrupted and the file which was being transferred when the interruption occurred still remains out there with nothing to differentiate it from the other files. I don't believe openssh uses .part files or any form of temporary filename during transfers. So when Duplicity resumes, it sees that file and thinks it transferred ok and begins with the next file.