duplicity-team team mailing list archive

[edso <question248111@xxxxxxxxxxxxxxxxxxxxx>]

Question #248111 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/248111

    Status: Open => Answered

edso proposed the following answer:
well done. yeah it's a shot in the dark and the error was on MacOSX ;(
but worth a shot.

when retrying try to account for your long path names in some way.

another idea: try your original dataset again, but with a different
volumesize this time. maybe the bug lurks there?

..ede/duply.net

On 11.05.2014 19:51, Rodrigo Alvarez wrote:
> Question #248111 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/248111
> 
> Rodrigo Alvarez gave more information on the question:
> The test gave a negative results.
> 
> I created a set of ~150,000 files, all small text files, and mostly hard
> linked copies of the same file.  Then I ran a duplicity backup, a verify
> and a 2nd backup.  The 2nd backup did not re-add any additional files.
> This does not support the theory of a python array capping ~92000 files.
> Logs at
> http://sira.duckdns.org/temp/duplicity_logs_test_2014_05_11.tar.gz
> 
> I will try creating the same set with longer file names to push python's
> memory footprint but it seems a shot in the dark.
> 
> +R
> 
> On May 11, 2014, at 2:46 AM, edso <question248111@xxxxxxxxxxxxxxxxxxxxx>
> wrote:
> 
>> Your question #248111 on Duplicity changed:
>> https://answers.launchpad.net/duplicity/+question/248111
>>
>>    Status: Open => Answered
>>
>> edso proposed the following answer:
>> On 11.05.2014 10:06, Rodrigo Alvarez wrote:
>>> Question #248111 on Duplicity changed:
>>> https://answers.launchpad.net/duplicity/+question/248111
>>>
>>> Rodrigo Alvarez posted a new comment:
>>> The smaller mirror test (created using cp -laR and then removing
>>> directories from 2000 through 2009) showed no issues.  This rules out
>>> that the problem was a simple name-comparison issue.
>>>
>>
>> hmm.. weird. maybe you should stick to the original test case albeit big
>> it at least sports the problem.
>>
>> can you confirm that you 
>> - ran a full
>> - verify without differences
>> - ran a second backup that found and added files
>> ?
>>
>> shot in the dark. maybe you hit a limit with the amount of files
>> somehow?
>>
>> ..ede/duply.net
>>
>> -- 
>> If this answers your question, please go to the following page to let us
>> know that it is solved:
>> https://answers.launchpad.net/duplicity/+question/248111/+confirm?answer_id=11
>>
>> If you still need help, you can reply to this email or go to the
>> following page to enter your feedback:
>> https://answers.launchpad.net/duplicity/+question/248111
>>
>> You received this question notification because you asked the question.
>

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.