|
|
> I tried duplicity 0.4.10 and 0.4.11 with bot 0.9d and 1.2a, after a
> few uploaded files I'm always getting this error: Is this specific to your use of S3? That is, have you tried this and seen it work with another backend? The reason I ask is: > # duplicity / s3+http://mybucket/backup/ In combination with: > buf = self.infile.read(length) > IOError: [Errno 22] Invalid argument If you are backing up your entire file system, you are going to be including a lot of special files in that backup (such as /proc). My guess is that you have not seen this suceed with another backend already? If so I suggest that you re-run with -v5, such that you will see which file was being processed when it failed. I suspect whichever file that is, is going to have some kind of special property that prevents it being read. Likely, you're going to end up wanting to exclude things like /proc and /dev. -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller@xxxxxxxxxxxx>' Key retrieval: Send an E-Mail to getpgpkey@xxxxxxxxx E-Mail: peter.schuller@xxxxxxxxxxxx Web: http://www.scode.org
Duplicity-talk mailing list Duplicity-talk@xxxxxxxxxx http://lists.nongnu.org/mailman/listinfo/duplicity-talk
Thread at a glance:
Previous Message by Date:IOErrors with S3I tried duplicity 0.4.10 and 0.4.11 with bot 0.9d and 1.2a, after a few uploaded files I'm always getting this error: # duplicity / s3+http://mybucket/backup/ GnuPG passphrase: Retype to confirm: No signatures found, switching to full backup. Traceback (most recent call last): File "/usr/bin/duplicity", line 463, in <module> with_tempdir(main) File "/usr/bin/duplicity", line 458, in with_tempdir fn() File "/usr/bin/duplicity", line 449, in main full_backup(col_stats) File "/usr/bin/duplicity", line 155, in full_backup bytes_written = write_multivol("full", tarblock_iter, globals.backend) File "/usr/bin/duplicity", line 87, in write_multivol globals.gpg_profile,globals.volsize) File "/usr/lib/python2.5/site-packages/duplicity/gpg.py", line 213, in GPGWriteFile data = block_iter.next(bytes_to_go).data File "/usr/lib/python2.5/site-packages/duplicity/diffdir.py", line 407, in next result = self.process(self.input_iter.next(), size) File "/usr/lib/python2.5/site-packages/duplicity/diffdir.py", line 487, in process data, last_block = self.get_data_block(fp, size - 512) File "/usr/lib/python2.5/site-packages/duplicity/diffdir.py", line 508, in get_data_block buf = fp.read(read_size) File "/usr/lib/python2.5/site-packages/duplicity/diffdir.py", line 338, in read buf = self.infile.read(length) IOError: [Errno 22] Invalid argument Next Message by Date:Re: Support for hard links> any idea when duplicity will support hard links? Or is the > information on the duplicity web page about not supporting hard links > out of date? I was hoping someone would respond with something definitive, but in the abscence of that, here is some hand waving: Short version: No. Long version: I have no information historically here, but looking around the source there definitely seems to be code that cares about hard links and tries to detect that a file is hardlinked to an already archived file. There is also a unit test which tests that the tarfile library preserves this information. However, a trivial test where I backup a file hardlinked to another, results in a resulting archive of a size which indicates no hard link optimization was done. -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller@xxxxxxxxxxxx>' Key retrieval: Send an E-Mail to getpgpkey@xxxxxxxxx E-Mail: peter.schuller@xxxxxxxxxxxx Web: http://www.scode.org pgpHgSC3Ca633.pgp Description: PGP signature _______________________________________________ Duplicity-talk mailing list Duplicity-talk@xxxxxxxxxx http://lists.nongnu.org/mailman/listinfo/duplicity-talk Previous Message by Thread:IOErrors with S3I tried duplicity 0.4.10 and 0.4.11 with bot 0.9d and 1.2a, after a few uploaded files I'm always getting this error: # duplicity / s3+http://mybucket/backup/ GnuPG passphrase: Retype to confirm: No signatures found, switching to full backup. Traceback (most recent call last): File "/usr/bin/duplicity", line 463, in <module> with_tempdir(main) File "/usr/bin/duplicity", line 458, in with_tempdir fn() File "/usr/bin/duplicity", line 449, in main full_backup(col_stats) File "/usr/bin/duplicity", line 155, in full_backup bytes_written = write_multivol("full", tarblock_iter, globals.backend) File "/usr/bin/duplicity", line 87, in write_multivol globals.gpg_profile,globals.volsize) File "/usr/lib/python2.5/site-packages/duplicity/gpg.py", line 213, in GPGWriteFile data = block_iter.next(bytes_to_go).data File "/usr/lib/python2.5/site-packages/duplicity/diffdir.py", line 407, in next result = self.process(self.input_iter.next(), size) File "/usr/lib/python2.5/site-packages/duplicity/diffdir.py", line 487, in process data, last_block = self.get_data_block(fp, size - 512) File "/usr/lib/python2.5/site-packages/duplicity/diffdir.py", line 508, in get_data_block buf = fp.read(read_size) File "/usr/lib/python2.5/site-packages/duplicity/diffdir.py", line 338, in read buf = self.infile.read(length) IOError: [Errno 22] Invalid argument Next Message by Thread:Re: IOErrors with S3On Thu, 7 Aug 2008 21:47:27 +0200 Peter Schuller <peter.schuller@xxxxxxxxxxxx> wrote: > Likely, you're going to end up wanting to exclude things like /proc > and /dev. These are the things I always exclude, in case suggestions are desired: /dev /lost+found /media (don't want to back up any CD's or external disks I happen to have mounted during backup) /mnt (this usually refers to another media I'd just rather backup separately anyway) /proc /sys /tmp signature.asc Description: PGP signature _______________________________________________ Duplicity-talk mailing list Duplicity-talk@xxxxxxxxxx http://lists.nongnu.org/mailman/listinfo/duplicity-talk
|
|
