diff options
| author |  https://launchpad.net/~eythian <eythian@web> | 2013-07-12 10:43:23 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-07-12 10:43:23 +0000 |
| commit | 7e7a56ffb771ede030a86d89afb3c3e7487dd333 (patch) | |
| tree | 2a300e0638fe6d73ed7d1f4fb486fbb63465fc88 | |
| parent | 43d079e483bdb2b85d51d1a5cf9f52cb554386bf (diff) | |
Added a comment
| -rw-r--r-- | doc/bugs/Truncated_file_transferred_via_S3/comment_5_f86f83c89300f255e730ddd23f876f61._comment | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/bugs/Truncated_file_transferred_via_S3/comment_5_f86f83c89300f255e730ddd23f876f61._comment b/doc/bugs/Truncated_file_transferred_via_S3/comment_5_f86f83c89300f255e730ddd23f876f61._comment new file mode 100644 index 000000000..742d22e2d --- /dev/null +++ b/doc/bugs/Truncated_file_transferred_via_S3/comment_5_f86f83c89300f255e730ddd23f876f61._comment @@ -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> +"""]] |