diff options
| author |  darkfeline <darkfeline@web> | 2015-10-18 23:58:08 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-10-18 23:58:08 +0000 |
| commit | d7b386f66166df0e9e9379533115acc9e7425f31 (patch) | |
| tree | b9f260d555fdd34d09efd1d6784258937566a19c | |
| parent | 46515ed90e84a123794c261e6d733cf2ba9091ef (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/Help_fixing_S3_mistake/comment_4_34333d0f3eeaf2929089535632759ba1._comment | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/forum/Help_fixing_S3_mistake/comment_4_34333d0f3eeaf2929089535632759ba1._comment b/doc/forum/Help_fixing_S3_mistake/comment_4_34333d0f3eeaf2929089535632759ba1._comment new file mode 100644 index 000000000..ddb5c0fb6 --- /dev/null +++ b/doc/forum/Help_fixing_S3_mistake/comment_4_34333d0f3eeaf2929089535632759ba1._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="darkfeline" + subject="comment 4" + date="2015-10-18T23:58:08Z" + content=""" +Actually, I suspect that I may have done more damage than I had initially thought. + +Is there a way to check whether the repo still has information about a file's whereabouts, especially how it was chunked on an S3 remote? I'm not sure if that information still exists or not. If it doesn't exist anymore, then recovery is likely impossible. + +If this information still exists in the repo, I can reconstitute the files by hand (script) if necessary and reinject them. I'm assuming that I can decrypt them using my private key? +"""]] |