duplicity-team team mailing list archive

[Kenneth Loafman <question163116@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

Kenneth Loafman proposed the following answer:
How did you increase ulimit?  Did you sign out and back in?  Increasing
files is a very cheap setting resource wise.  You can find out how to
increase it permanently by searching Google for 'linux num_files limit'.

Given the number of incrementals you have, duplicity will use a couple of
thousand file handles, 3 or 4 per incremental, so 50k is way over,

...Ken

On Sat, Jul 16, 2011 at 9:01 AM, Rodrigo Alvarez <
question163116@xxxxxxxxxxxxxxxxxxxxx> wrote:

> Question #163116 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/163116
>
>    Status: Answered => Open
>
> Rodrigo Alvarez is still having a problem:
> Patching the manifest worked and I was able to move past Vol2.  However,
> now I'm getting an OSError: [Errno 24] Too many open files.   I have
> increased my user's limit for open files from 1024 to 50000 (fifty
> thousand) and this does not change anything.   During the process,
> duplicity uses about 30 GB of space on the scratch drive (75GB are still
> available).  Please help: the complete output log can be found here:
> http://www.stanford.edu/~rodrigoa/Temp/duplicity_verify_log_2011-07-16.txt
>
> For posterity:  To patch the manifest I first had to find the corrupted
> manifest.  I did this by copying the gpged manifests, decrypting them,
> concatenating them and searching for the wrong Hash. Once I identified
> the suspect manuscript I patched it, encrypted it and replaced the
> original.  Finally I replaced the patched manifest in duplicity's cache
> so that it would be picked up during the process.
>
> $ temp_location="temp_manifests2/"
> $ full_file="all_manifests"
> $ # Copy Original Manifest to temp location
> $ cp *.manifest.gpg $temp_location
> $ cd $temp_location
> $ gpg --multifile --decrypt *.gpg
> $ rm *.gpg
> $ i=`ls`; for f in $i; do echo -e "\n\n$f" >> $full_file; cat $f >>
> $full_file;done
> $ # Used gedit to find the wrong hash in all manuscripts and then patched
> the suspect manuscript file
> $ gpg --symmetric Manifest_file_name
> $ # Finaly delete duplicity cache so that it uses the patched manifest.
>
> --
> 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
>

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