From d37bf244a17147acbf92340fb6095c2df9a7fc41 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 5 Jul 2013 16:49:33 +0000 Subject: Added a comment --- .../comment_1_5962358e6067448f633cc0eaf42f9ca7._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/Truncated_file_transferred_via_S3/comment_1_5962358e6067448f633cc0eaf42f9ca7._comment (limited to 'doc/bugs/Truncated_file_transferred_via_S3') 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. +"""]] -- cgit v1.2.3