From 5262e6a372553e39ce70fdfc6298540874355713 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 23 Jul 2014 16:46:15 -0400 Subject: [PATCH] recommend users not change the chunksize Suppose A is 10 mb, and B is 20 mb, and the upload speed is the same. If B starts first, when A will overwrite the file it is uploading for the 1st chunk. Then A uploads the second chunk, and once A is done, B finishes the 1st chunk and uploads its second. We now have 1(from A), 2(from B), so data loss. --- doc/special_remotes/directory.mdwn | 2 +- doc/special_remotes/webdav.mdwn | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/special_remotes/directory.mdwn b/doc/special_remotes/directory.mdwn index b79cf75441..96d5938213 100644 --- a/doc/special_remotes/directory.mdwn +++ b/doc/special_remotes/directory.mdwn @@ -31,7 +31,7 @@ remote: The value can use specified using any commonly used units. Example: `chunksize=100 megabytes` Note that enabling chunking on an existing remote with non-chunked - files is not recommended. + files is not recommended; nor is changing the chunksize. Setup example: diff --git a/doc/special_remotes/webdav.mdwn b/doc/special_remotes/webdav.mdwn index 21b213ee56..871540a979 100644 --- a/doc/special_remotes/webdav.mdwn +++ b/doc/special_remotes/webdav.mdwn @@ -35,7 +35,7 @@ the webdav remote. The value can use specified using any commonly used units. Example: `chunksize=75 megabytes` Note that enabling chunking on an existing remote with non-chunked - files is not recommended. + files is not recommended, nor is changing the chunksize. Setup example: