diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2013-07-05 16:49:33 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-07-05 16:49:33 +0000 |
| commit | d37bf244a17147acbf92340fb6095c2df9a7fc41 (patch) | |
| tree | 739c6434fa2f83bef77dbabcf461331232ea1d81 /doc/bugs/Truncated_file_transferred_via_S3 | |
| parent | 0878f9051291c5035c3c0ab3beefab4871410ed4 (diff) | |
Added a comment
Diffstat (limited to 'doc/bugs/Truncated_file_transferred_via_S3')
| -rw-r--r-- | doc/bugs/Truncated_file_transferred_via_S3/comment_1_5962358e6067448f633cc0eaf42f9ca7._comment | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/Truncated_file_transferred_via_S3/comment_1_5962358e6067448f633cc0eaf42f9ca7._comment b/doc/bugs/Truncated_file_transferred_via_S3/comment_1_5962358e6067448f633cc0eaf42f9ca7._comment new file mode 100644 index 000000000..6a05b9750 --- /dev/null +++ b/doc/bugs/Truncated_file_transferred_via_S3/comment_1_5962358e6067448f633cc0eaf42f9ca7._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.193" + subject="comment 1" + date="2013-07-05T16:49:33Z" + content=""" +Did you get a chance to run `git annex fsck` on the file? I'd hope it would detect this problem. + +It's certianly possible for data to get corrupted somehow in transit. git-annex does not check that it got the expected contents until a fsck happens. +"""]] |