diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-05-12 15:11:28 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-05-12 15:11:28 -0400 |
| commit | 747c85a07079692c2e168b469b1101a91a4f21a1 (patch) | |
| tree | 9fe7bc28fb50e5a40567fb923afaf06de63cb049 | |
| parent | f33fe00e45e91e8ae6d22136a68ff4f6070f8544 (diff) | |
response
| -rw-r--r-- | doc/forum/Fails_to_get_file_from_s3._How_to_recover__63__/comment_9_e021705e0fae6645a0b6459757260084._comment | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/forum/Fails_to_get_file_from_s3._How_to_recover__63__/comment_9_e021705e0fae6645a0b6459757260084._comment b/doc/forum/Fails_to_get_file_from_s3._How_to_recover__63__/comment_9_e021705e0fae6645a0b6459757260084._comment new file mode 100644 index 000000000..ece2c012c --- /dev/null +++ b/doc/forum/Fails_to_get_file_from_s3._How_to_recover__63__/comment_9_e021705e0fae6645a0b6459757260084._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 9""" + date="2016-05-12T19:04:00Z" + content=""" +My best guess at the moment is that the corruption must have something to +do with using a partsize. + +Since you were able to get at the corrupted files, can you characterize at +all how they were corrupted? + +In particular, did the corruption start at some multiple of N GiB? +into the file? If so, that would correlate with your 1 GiB part size. + +Or was it just a small area of corruption? + +Or is the corrupt file truncated? +"""]] |