From 6a832b7173bce296239dc9db966a3f0e95cbbede Mon Sep 17 00:00:00 2001 From: Nick Craig-Wood Date: Sun, 27 Jan 2019 21:09:11 +0000 Subject: [PATCH] qingstor: default --qingstor-upload-concurrency to 1 to work around bug If the upload concurrency is set > 1 then the hash becomes corrupted. The upload is fine, and can be downloaded fine, however the hash is no longer the md5sum of the object. It is not known whether this is rclone's fault or a bug at QingStor. --- backend/qingstor/qingstor.go | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/backend/qingstor/qingstor.go b/backend/qingstor/qingstor.go index edd4b3a0b..57b1b4408 100644 --- a/backend/qingstor/qingstor.go +++ b/backend/qingstor/qingstor.go @@ -101,10 +101,13 @@ enough memory, then increasing this will speed up the transfers.`, This is the number of chunks of the same file that are uploaded concurrently. +NB if you set this to > 1 then the checksums of multpart uploads +become corrupted (the uploads themselves are not corrupted though). + If you are uploading small numbers of large file over high speed link and these uploads do not fully utilize your bandwidth, then increasing this may help to speed up the transfers.`, - Default: 4, + Default: 1, Advanced: true, }}, })