© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
When mod priviledges are modified back to a typical 755, the extracted file "19950817 Fort Lauderdale 08.jpg" appears (image wise) as the first 75% of he original file. The lower 25% of the image is missing. So it seems that the last portion of the file has not been extracted.
I have identified the volume containing the failure The offending file
"19950817 Fort Lauderdale 08.jpg" exists across the volume boundary, spans 19
segments from th last part of vol582 into vol583. The first volume (vol582) produces a gpg fatal error. The second volume (vol583) does not (see below).
gpg --decrypt /media/
You need a passphrase to unlock the secret key for
user: "First Last(Duplicity key) <email address hidden>"
2048-bit RSA key, ID 73B4F60A, created 2010-09-02 (main key ID 8ABB1A41)
gpg: gpg-agent is not available in this session
gpg: encrypted with 2048-bit RSA key, ID 73B4F60A, created 2010-09-02
"FIrst Last(Duplicity key) <email address hidden>"
gpg: fatal: zlib inflate problem: incorrect data check
secmem usage: 2400/5440 bytes in 5/15 blocks of pool 5632/32768
When duplicity-
is decrypted and extracted, the volume snapshot appears as:
.
.
.
multivol_
multivol_
multivol_
multivol_
multivol_
multivol_
multivol_
multivol_
multivol_
multivol_
multivol_
multivol_
multivol_
multivol_
multivol_
multivol_
multivol_
The sequential volume duplicity-
(vol583):
gpg --decrypt /media/
You need a passphrase to unlock the secret key for
user: "First Last(Duplicity key) <email address hidden>"
2048-bit RSA key, ID 73B4F60A, created 2010-09-02 (main key ID 8ABB1A41)
gpg: gpg-agent is not available in this session
gpg: encrypted with 2048-bit RSA key, ID 73B4F60A, created 2010-09-02
"First Last(Duplicity key) <email address hidden>"
gpg: Signature made Fri 04 Feb 2011 10:50:42 PM PST using RSA key ID 8ABB1A41
gpg: Good signature from "First Last(Duplicity key) <email address hidden>"
When duplicity-
is decrypted and extracted, the volume snapshot appears as:
multivol_
multivol_
multivol_
multivol_
multivol_
multivol_
multivol_
multivol_
.
.
.
So it appears that duplicity gives up and quits (even with ignore-errors enabled) when gpg produces the fatal error.
Also note that despite the error issued by gpg on vol582, extraction of the data from both vol582 and vol583 tar files following gpg decryption produces a complete and correct file.
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# cat "multivol_
root@SOUTH:~# md5sum myphoto.jpg
88adbf2eaf72859
root@SOUTH:~# md5sum /media/
88adbf2eaf72859
If there is a work-around for this, I would be most appreciative.
-W