removed

diff --git a/doc/special_remotes/rclone/comment_5_414559099884a972943586cf03d613a4._comment b/doc/special_remotes/rclone/comment_5_414559099884a972943586cf03d613a4._comment
deleted file mode 100644 (file)
index 5e7837a..0000000
--- a/doc/special_remotes/rclone/comment_5_414559099884a972943586cf03d613a4._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="mike@2d6d71f56ce2a992244350475251df87c26fe351"
- nickname="mike"
- avatar="http://cdn.libravatar.org/avatar/183fa439752e2f0c6f39ede658d81050"
- subject="corruption using git-annex-remote-rclone"
- date="2024-09-27T07:39:06Z"
- content="""
-Perhaps Joey can help me out here a bit with some background knowledge:
-
-I've been seeing sporadic corruption with this setup:
-- chunking
-- encryption
-- old helper program git-annex-remote-rclone
-- rclone's pcloud backend
-
-At it seems, rclone keeps partial files under the name of the full file when a transfer is interrupted, for the pcloud backend. (This is for rclone <= 1.67.0; 1.68.0 has changes for pcloud, which may fix this.) My theory how the corruption might have happened:
-
-- First interrupted run of git-annex uploads chunks A and a partial(!) chunk B
-- Second run skips chunks A and B(!) and, say, the rest of the chunks (C and D)
-- At the end we have uploaded A, C and D and a corrupted/partial chunk B
-
-Joey: Is this a possible error scenario?
-
-"""]]