summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar annexuser <annexuser@web>2016-04-30 17:23:33 +0000
committerGravatar admin <admin@branchable.com>2016-04-30 17:23:33 +0000
commit6534d87390b6386370abc5fe6fc9bf05bb5269cb (patch)
tree0bf283c6bdec4a320d0ddf1c262fefc689d40876
parent65a3a0f23eb49d06b6a7ed54ee71a3c0c6c24a4f (diff)
-rw-r--r--doc/forum/Fails_to_get_file_from_s3._How_to_recover__63__.mdwn16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/forum/Fails_to_get_file_from_s3._How_to_recover__63__.mdwn b/doc/forum/Fails_to_get_file_from_s3._How_to_recover__63__.mdwn
new file mode 100644
index 000000000..e6bfd4a91
--- /dev/null
+++ b/doc/forum/Fails_to_get_file_from_s3._How_to_recover__63__.mdwn
@@ -0,0 +1,16 @@
+I have an annex that has an s3 special remote. The s3 remote has been configured with shared encryption and it uses partsize (not chunking). Currently when I try to get a file from the s3 remote, it fails:
+
+ $ git annex get mybigfile.tbz.gpg
+ get mybigfile.tbz.gpg (from s3...)
+ 76% 10.6MB/s 57sgpg: WARNING: encrypted message has been manipulated!
+
+ Unable to access these remotes: s3
+
+ Try making some of these repositories available:
+ 15ac19e4-223a-4c81-b7f7-797b9b026b86 -- [s3]
+
+ (Note that these git remotes have annex-ignore set: origin)
+ failed
+ git-annex: get: 1 failed
+
+The file is about 3GB. This happens consistently at 76%. No other copy of the file exists. Is there some way I can get the file from s3, either without git annex or just have git annex ignore the error, so that I can inspect the file locally and see if there is anything wrong with it?