mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
https://launchpad.net/~eythian 2013-07-12 10:43:23 +00:00 • committed by admin
parent 9e65eecf38
commit 90a087d658
1 changed files with 16 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
doc/bugs/Truncated_file_transferred_via_S3/comment_5_f86f83c89300f255e730ddd23f876f61._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="https://launchpad.net/~eythian"
nickname="eythian"
subject="comment 5"
date="2013-07-12T10:43:23Z"
content="""
Good thing I set up obnam a while ago :)
Anyway, yes, a very similar pattern of corruption can be seen here. It might be worth nothing that it starts in a different place in the file. The one I'm looking at now begins at byte 0x1C, whereas it was a little bit further into the file previously.
I created a large file that'd make the issue really clear and synced it over, and of course, everything worked perfectly.
Here is a pair of small files that shows the problem, from around the 0x4BC mark.
<http://www.kallisti.net.nz/~robin/good-bad-annex-files.tar.gz>
"""]]