diff options
| author |  http://svario.it/gioele <gioele@web> | 2014-04-24 14:52:23 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-04-24 14:52:23 +0000 |
| commit | 120f95b4c5092c4c2275dac1332e9bf66ce38482 (patch) | |
| tree | ba7cee2c18f4391c70739cc410c1347e835e223f | |
| parent | 01580037449496d78f4d19e86d689b1d65d0e200 (diff) | |
new topic "Checking for missing files in S3 (reduced redundancy)"
| -rw-r--r-- | doc/forum/Checking_for_missing_files_in_S3___40__reduced_redundancy__41__.mdwn | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/forum/Checking_for_missing_files_in_S3___40__reduced_redundancy__41__.mdwn b/doc/forum/Checking_for_missing_files_in_S3___40__reduced_redundancy__41__.mdwn new file mode 100644 index 000000000..97299a966 --- /dev/null +++ b/doc/forum/Checking_for_missing_files_in_S3___40__reduced_redundancy__41__.mdwn @@ -0,0 +1,5 @@ +I would like to use git-annex with [S3 reduced redundancy storace (RRS)](https://aws.amazon.com/s3/faqs/#rrs_anchor), a cheaper S3 service with an higher chance of seeing your files disappear overnight. This means that git-annex may think that a certain files has been copied to a S3 remote while, in fact, it is no longer there. + +I would like to check that the files S3 are really there and, if some files are not, record that we lost that copy. In the case of S3, either the data is there and it is complete or it is not there at all, so there is no need to check the data itself, just the presence of the files. + +Is there a way to check that all the files that are supposed to be in a S3 remote are still there? |