diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawkexhIpGcYa22aPQtLm-StpHiF-MHYPh5w <Robie@web> | 2013-06-10 17:24:34 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-06-10 17:24:34 +0000 |
| commit | cadf340249e8760f826861ae2e50473534788926 (patch) | |
| tree | f66cd3a3dba2e4af724c0a6b7c7f456a372c0a1b /doc/bugs/Glacier_remote_uploads_duplicates | |
| parent | 092b29409cc2f04e2bff4f72a376091b206d6776 (diff) | |
Added a comment
Diffstat (limited to 'doc/bugs/Glacier_remote_uploads_duplicates')
| -rw-r--r-- | doc/bugs/Glacier_remote_uploads_duplicates/comment_6_feea067d6856af2840604782b29af86a._comment | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/bugs/Glacier_remote_uploads_duplicates/comment_6_feea067d6856af2840604782b29af86a._comment b/doc/bugs/Glacier_remote_uploads_duplicates/comment_6_feea067d6856af2840604782b29af86a._comment new file mode 100644 index 000000000..2a140eb49 --- /dev/null +++ b/doc/bugs/Glacier_remote_uploads_duplicates/comment_6_feea067d6856af2840604782b29af86a._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawkexhIpGcYa22aPQtLm-StpHiF-MHYPh5w" + nickname="Robie" + subject="comment 6" + date="2013-06-10T17:24:34Z" + content=""" +This seems reasonable to me. + +One other possibility that you could end up with a duplicate: if `glacier-cli`'s cache is not up to date. For example: hosts A and B both have (the same) annex with the same Glacier special remote defined. Host A copies a file to Glacier. On host B, the `glacier-cli` cache doesn't know about the file, and so a copy to Glacier on host B also succeeds. When the cache is later brought up to date `glacier vault sync`, then the duplicate appears. + +I'm not sure what we can do about this. Perhaps we need to accept that duplicates will occur, and handle them more gracefully. +"""]] |