duplicity-team team mailing list archive

[Kenneth Loafman <kenneth@xxxxxxxxxxx>]

If the OS does not return an error, duplicity will not see it.  Since the
OS is not reporting those errors, it may be that they were retried
successfully.  It's hard to tell from your message.

Do you have a log file of the run?  If so, please post it after obscuring
any sensitive info.


On Fri, Mar 7, 2014 at 5:46 AM, Daniel Hobi <
question245129@xxxxxxxxxxxxxxxxxxxxx> wrote:

> New question #245129 on Duplicity:
> https://answers.launchpad.net/duplicity/+question/245129
>
> We are using Duplicity 0.6.22 on Ubuntu 10.04 LTS.
> A full backup (571 GB) is procesed by duplicity (using symetrical
> encryption) to a mounted CIFS share with return code 0.
>
> However, in the kern.log we see, during the time of the full backup,
> messages such as:
> CIFS VFS: No response to cmd 47 mid 20561
> CIFS VFS: Write2 ret -11, wrote 0
>
> During the restore of this full backup duplicity fails with error code: 21
> (= mismatched_hash)
> A manual check of the encrypted duplicity volumes confirms that some
> (about 12) volumes are corrupt.
>
> Our main question is: Why does duplicity not detect the CIFS problems
> underneath during the backup?
>
> Daniel
>
> --
> You received this question notification because you are a member of
> duplicity-team, which is an answer contact for Duplicity.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~duplicity-team
> Post to     : duplicity-team@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~duplicity-team
> More help   : https://help.launchpad.net/ListHelp
>