diff options
author | Joey Hess <joeyh@joeyh.name> | 2015-07-02 12:53:47 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2015-07-02 12:53:47 -0400 |
commit | 22b40e1bcea274161daffe79c44f4ce1a920f4e1 (patch) | |
tree | 5ff6e27731be4ecad418f838052bc31e64c5586d /doc | |
parent | 0e719d274cbd33bae28a8bd712d793024ed9b543 (diff) |
comment
Diffstat (limited to 'doc')
-rw-r--r-- | doc/todo/S3_fsck_support/comment_3_2b96f61188b2ada729a284e95fc89dab._comment | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/todo/S3_fsck_support/comment_3_2b96f61188b2ada729a284e95fc89dab._comment b/doc/todo/S3_fsck_support/comment_3_2b96f61188b2ada729a284e95fc89dab._comment new file mode 100644 index 000000000..fea047754 --- /dev/null +++ b/doc/todo/S3_fsck_support/comment_3_2b96f61188b2ada729a284e95fc89dab._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2015-07-02T16:43:03Z" + content=""" +Not knowing how S3's backend is implemented, I have to assume that, in +order to get the advertised number of 9's of reliability, it involves some +replication of data, as well as some method to detect if a bit has flipped +or a drive has died, and recover. + +This is requesting that git-annex ask S3 for a md5sum, and compare it +against a md5sum that it, presumably, keeps track of locally. If the two +are different, git-annex could tell that S3 has lost data. But, git-annex is +in a much worse position to tell if S3 has lost data then S3 itself is. +It seems very unlikely that this extra checking would ever detect a problem +that S3 didn't itself detect and fix (or in the 0.00001% case, +fail to fix and delete the lost file?) + +Bit flips during transfer seem more likely than that. `poContentMD5` could +help guard against those. +"""]] |