duplicity-team team mailing list archive
-
duplicity-team team
-
Mailing list archive
-
Message #01790
Re: Missing-info bug brainstorming
I wish, but no, there is not. Maybe that should be the first task.
On Fri, Sep 20, 2013 at 8:57 AM, Michael Terry <mike@xxxxxxxxxxx> wrote:
> Is there a nice overview of the format/syntax/details of the sigtar
> format? It's just librsync's checksum data right? And with instructions
> for "copy 13 bytes from basis file" or "add these 32 bytes"?
>
> It'd help me understand how these bugs might occur if I knew exactly what
> was happening with the sigtar.
>
> -mt
>
>
> On 20 September 2013 09:52, Kenneth Loafman <kenneth@xxxxxxxxxxx> wrote:
>
>> Will take another look at restart and so forth and we can compare notes
>> later. There is probably a very simple fix for this, the problem is
>> finding it.
>>
>>
>>
>> On Fri, Sep 20, 2013 at 8:47 AM, <edgar.soldin@xxxxxx> wrote:
>>
>>> On 20.09.2013 15:41, Michael Terry wrote:
>>> > So as I speculate in a recent merge [1], I think bug 1155345 <
>>> https://code.launchpad.net/bugs/1155345>, bug 720525 <
>>> https://code.launchpad.net/bugs/720525>, and bug 662442 <
>>> https://code.launchpad.net/bugs/662442> may all have the same
>>> underlying cause: a missing diff or snapshot entry in the chain.
>>> >
>>> > I also imagine that this is due to a bug when restarting a backup,
>>> just because that seems likely with this sort of issue.
>>> >
>>> > Maybe a file that has a diff entry in sigtar.part has its actual diff
>>> contents in the vol file deleted when resuming? (We do delete the last
>>> volume when resuming in case it didn't finish.) But I wasn't able to
>>> create the situation manually.
>>> >
>>> > I just figured I'd ask the brain trust if they could brainstorm any
>>> ways this situation could occur... It would be lovely to kill all these
>>> long-standing bugs in one fell swoop.
>>> >
>>> > [1]
>>> https://code.launchpad.net/~mterry/duplicity/catch-seq-copy-error/+merge/186106<
>>> https://code.launchpad.net/%7Emterry/duplicity/catch-seq-copy-error/+merge/186106
>>> >
>>> >
>>> > -mt
>>> >
>>>
>>> would like to help, but wrt. resuming i am totally out of the loop..
>>> sorry. ede
>>>
>>> _______________________________________________
>>> 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
>>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
References