From f58fb5a6100e3e9e7a8ef109d86aac0a21b75b7f Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 27 Apr 2021 12:24:36 -0400 Subject: [PATCH] comment --- ...t_1_a2fbf6a34c531224b0f870550af4ac22._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/fsck_of_encrypted_remote_fails_w__47___multiple_jobs/comment_1_a2fbf6a34c531224b0f870550af4ac22._comment diff --git a/doc/bugs/fsck_of_encrypted_remote_fails_w__47___multiple_jobs/comment_1_a2fbf6a34c531224b0f870550af4ac22._comment b/doc/bugs/fsck_of_encrypted_remote_fails_w__47___multiple_jobs/comment_1_a2fbf6a34c531224b0f870550af4ac22._comment new file mode 100644 index 0000000000..64c790da48 --- /dev/null +++ b/doc/bugs/fsck_of_encrypted_remote_fails_w__47___multiple_jobs/comment_1_a2fbf6a34c531224b0f870550af4ac22._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2021-04-27T16:20:41Z" + content=""" +The command that you show failing does not seem to have concurrency +enabled. Then you explicitly disable concurrency with -J 1 and it succeeds. +Do you have annex.jobs set, and if so, to what? + +There is something very odd about "(checking s3...) (checking s3...) +(checking s3...)" etc. I suspect you also have chunking enabled, and it is +displaying that once per chunk, in which case it's probably not much of a +clue about the problem. However, it highlights that you have really not +explained how this remote is set up; it would be useful to provide enough +information to reproduce the bug from scratch. +"""]]