Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: duplicity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
Marking invalid because duplicity does not support sparse files, yet.
** Changed in: duplicity
Status: In Progress => Invalid
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
--
You received this bug notification because you are a member of
Incr backup ran successfully with the sparse file excluded.
---
NOTICE 1
. --[ Backup Statistics ]--
. StartTime 1471995038.09 (Tue Aug 23 23:30:38 2016)
. EndTime 1472019526.98 (Wed Aug 24 06:18:46 2016)
. ElapsedTime 24488.90 (6 hours 48 minutes 8.90 seconds)
.
Yep, exclude that and it should work.
On Tue, Aug 23, 2016 at 6:33 AM, Peter Van Rompaey wrote:
> Re-ran the incremental backup, but it fails with the same error while
> adding /var/log/lastlog, which is a sparse file with a reported size of
> 36Gb, but actually only 56k on
Re-ran the incremental backup, but it fails with the same error while
adding /var/log/lastlog, which is a sparse file with a reported size of
36Gb, but actually only 56k on disk. Can this be the cause?
---
(duplicity-venv) # ls -l /var/log/lastlog
-rw-rw-r-- 1 root utmp 367219431264 Aug 23 09:57
# duplicity cleanup --force --no-encryption $BUCKET
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Wed Aug 17 08:38:55 2016
No extraneous files found, nothing deleted in cleanup.
Collection-status gives me:
Found primary backup chain with matching signature
It's possible that the last incremental was corrupted. Try this:
- duplicity cleanup --force
- remove the last incremental backup, easiest is by date in the filename
- duplicity inc -v9
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
** Changed in: duplicity
Status: Invalid => In Progress
** Changed in: duplicity
Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman)
** Changed in: duplicity
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Package: librsync1
Version: 0.9.7-10
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1612554
Title:
duplicity backup fails with OverflowError: size does not fit in an int
Status in
do this:
$ apt-cache show librsync1
That will display the version.
On Mon, Aug 22, 2016 at 3:16 AM, Peter Van Rompaey wrote:
> I didn't install any specific version, since it was included in the
> duplicity tarball:
>
> $ tar tf duplicity-0.7.09.tar.gz | grep -i rsync
>
I didn't install any specific version, since it was included in the duplicity
tarball:
$ tar tf duplicity-0.7.09.tar.gz | grep -i rsync
duplicity-0.7.09/duplicity/_librsyncmodule.c
duplicity-0.7.09/duplicity/librsync.py
duplicity-0.7.09/duplicity/backends/rsyncbackend.py
$ pip list
boto
What version of librsync?
On Fri, Aug 19, 2016 at 3:52 AM, Peter Van Rompaey wrote:
> Cried victory too soon, I'm afraid.
>
> I have:
> - compiled python 2.7.12 with the zlib patch
> - created a virtualenv with that version
> - installed duplicity in the virtualenv, along
Cried victory too soon, I'm afraid.
I have:
- compiled python 2.7.12 with the zlib patch
- created a virtualenv with that version
- installed duplicity in the virtualenv, along with lockfile and boto
The zlib test now succeeds:
(duplicity-venv) root@eniac:~# python -c "import
Marking as invalid since this problem is not with duplicity itself.
** Changed in: duplicity
Importance: Medium => Undecided
** Changed in: duplicity
Milestone: 0.7.10 => None
** Changed in: duplicity
Status: New => Invalid
--
You received this bug notification because you are a
Backup completed successfully with all >4Gb files excluded.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1612554
Title:
duplicity backup fails with OverflowError: size does not
Some more testing:
I installed a virtualenv with python 2.7.12 and duplicity 0.7.09, but
the problem still remains.
Then I ran the little test mentioned in
https://bugs.python.org/issue27130 which shows that zlib has a problem
zipping files > 4Gb:
When looking at the timestamps of the comments,
** Changed in: duplicity (Ubuntu)
Status: Invalid => New
** Also affects: duplicity
Importance: Undecided
Status: New
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Milestone: None => 0.7.10
--
You received this bug notification
Hi,
after performing these steps:
- apt-get remove duplicity
- add-apt-repository ppa:duplicity-team/ppa
- apt-get update
- apt-get install duplicity
I am now running:
$ duplicity --version
duplicity 0.7.09
And I still get the Overflow errors:
ERROR 30 OverflowError
. Traceback (most recent
This has been fixed for a couple of years. Please upgrade to a newer
version using the duplicity PPA or through the tarball in the download
area. The 0.6 series has been deprecated in the upstream. The 0.7
series is current.
Please be aware that you will need to 'apt-get remove duplicity'
Possibly related to https://bugs.python.org/issue23306
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1612554
Title:
duplicity backup fails with OverflowError: size does not fit in
20 matches
Mail list logo