duplicity assserion error with big backup on Hubic

[Ignacio Quezada]

I wanted to backup 1.3TB on Hubic, cf+hubic://default.

After many hours of uploading it ends up with an assertion error. If you retry, or try to list the files uploaded, it fails with the same error. Because of the size of the backup, I use --volsize 5000 (5gb, yes) and I realized that once my OS had killed the process because it had no memory left and apparently duplicity was taking 11GB ram.

duplicity 0.7.06
python 2.7.9
Debian GNU/Linux 8.3 (jessie)

The log attached is from when I retry to backup

[Kenneth Loafman (kenneth-loafman)]

Try adding --max-blocksize=20480 or larger to your backup command. That
will reduce the memory needed.

On Fri, Feb 26, 2016 at 1:46 AM, Ignacio Quezada <<email address hidden>
> wrote:

> Public bug reported:
>
> I wanted to backup 1.3TB on Hubic, cf+hubic://default.
>
> After many hours of uploading it ends up with an assertion error. If you
> retry, or try to list the files uploaded, it fails with the same error.
> Because of the size of the backup, I use --volsize 5000 (5gb, yes) and I
> realized that once my OS had killed the process because it had no memory
> left and apparently duplicity was taking 11GB ram.
>
>
> duplicity 0.7.06
> python 2.7.9
> Debian GNU/Linux 8.3 (jessie)
>
> The log attached is from when I retry to backup
>
> ** Affects: duplicity
> Importance: Undecided
> Status: New
>
> ** Attachment added: "duplicity log"
>
> https://bugs.launchpad.net/bugs/1550176/+attachment/4581564/+files/duplicity-inc.log
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/1550176
>
> Title:
> duplicity assserion error with big backup on Hubic
>
> Status in Duplicity:
> New
>
> Bug description:
> I wanted to backup 1.3TB on Hubic, cf+hubic://default.
>
> After many hours of uploading it ends up with an assertion error. If
> you retry, or try to list the files uploaded, it fails with the same
> error. Because of the size of the backup, I use --volsize 5000 (5gb,
> yes) and I realized that once my OS had killed the process because it
> had no memory left and apparently duplicity was taking 11GB ram.
>
>
> duplicity 0.7.06
> python 2.7.9
> Debian GNU/Linux 8.3 (jessie)
>
> The log attached is from when I retry to backup
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1550176/+subscriptions
>