From 5f0df3de7ed8f1d553d0e61a221c3973366c015a Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Thu, 2 Jun 2022 18:43:02 +0000 Subject: [PATCH 1/5] Added a comment: defending BTRFS --- ...mment_13_afae18b8b3a17f376b9a345059d9dbd4._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/bugs/get_is_busy_doing_nothing/comment_13_afae18b8b3a17f376b9a345059d9dbd4._comment diff --git a/doc/bugs/get_is_busy_doing_nothing/comment_13_afae18b8b3a17f376b9a345059d9dbd4._comment b/doc/bugs/get_is_busy_doing_nothing/comment_13_afae18b8b3a17f376b9a345059d9dbd4._comment new file mode 100644 index 0000000000..30ab1ceb36 --- /dev/null +++ b/doc/bugs/get_is_busy_doing_nothing/comment_13_afae18b8b3a17f376b9a345059d9dbd4._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="defending BTRFS" + date="2022-06-02T18:43:02Z" + content=""" +FWIW, may be just as a defender of BTRFS decided to share a \"terminal shot\" of screens from drogon -- you can see how busy it is (`top` and `dstat` at the bottom) downloading (>= 100MBps) and reading (70MBps) and saving (>200MBps) while there is a good number of parallel processes which have a number of parallel git-annex processes: +[screenshot](http://www.onerussian.com/tmp/busy-drogon-MVar-operation.png) + +and I don't know how well any other file system would have held up ;) +"""]] From 4a10d8382b0f37ab941e8397d9ed586d195d9696 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Fri, 3 Jun 2022 01:36:39 +0000 Subject: [PATCH 2/5] Added a comment: still reports about invalid option but doesn't fail --- ..._e3a79f9480a7123feb924f3c1e72ce62._comment | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 doc/bugs/gpgconf__58___invalid_option___34__--kill__34_____40__gpg_2.0.22__41___/comment_5_e3a79f9480a7123feb924f3c1e72ce62._comment diff --git a/doc/bugs/gpgconf__58___invalid_option___34__--kill__34_____40__gpg_2.0.22__41___/comment_5_e3a79f9480a7123feb924f3c1e72ce62._comment b/doc/bugs/gpgconf__58___invalid_option___34__--kill__34_____40__gpg_2.0.22__41___/comment_5_e3a79f9480a7123feb924f3c1e72ce62._comment new file mode 100644 index 0000000000..9a00b40e15 --- /dev/null +++ b/doc/bugs/gpgconf__58___invalid_option___34__--kill__34_____40__gpg_2.0.22__41___/comment_5_e3a79f9480a7123feb924f3c1e72ce62._comment @@ -0,0 +1,26 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="still reports about invalid option but doesn't fail" + date="2022-06-03T01:36:38Z" + content=""" +so I should try with outdated gpgconf on some older CentOS? ..already done - we do run annex tests daily on ndoli (part of discovery) now and apparently: tests passed, but it did have those reports + +``` +(git)smaug:/mnt/datasets/datalad/ci/git-annex-ci-client-jobs/builds/2022/06[master]git +$> tail result-ndoli-715/handle-result.yaml-154-7a381a8a-success/result-ndoli-715/git-annex-tmp.rc +0 + +$> tail result-ndoli-715/handle-result.yaml-154-7a381a8a-success/result-ndoli-715/git-annex-tmp.log +gpgconf: invalid option \"--kill\" +gpgconf: invalid option \"--kill\" +gpgconf: invalid option \"--kill\" +gpgconf: invalid option \"--kill\" +gpgconf: invalid option \"--kill\" ++ echo 'Elapsed time: 3278 seconds' +Elapsed time: 3278 seconds ++ cd /dartfs/rc/lab/D/DBIC/DBIC/archive/tmp ++ chmod -R +w 715 ++ rm -rf 715 +``` +"""]] From f9a7eb2f4980f2246e7e94e04ed7af7f5afc3a72 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Fri, 3 Jun 2022 01:40:17 +0000 Subject: [PATCH 3/5] Added a comment --- ..._981d6d42f411476d1a5e38d987af6035._comment | 34 +++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 doc/bugs/v8_conflict_resolution___40__adjusted_branch__41___teststuck/comment_4_981d6d42f411476d1a5e38d987af6035._comment diff --git a/doc/bugs/v8_conflict_resolution___40__adjusted_branch__41___teststuck/comment_4_981d6d42f411476d1a5e38d987af6035._comment b/doc/bugs/v8_conflict_resolution___40__adjusted_branch__41___teststuck/comment_4_981d6d42f411476d1a5e38d987af6035._comment new file mode 100644 index 0000000000..03f5774bd2 --- /dev/null +++ b/doc/bugs/v8_conflict_resolution___40__adjusted_branch__41___teststuck/comment_4_981d6d42f411476d1a5e38d987af6035._comment @@ -0,0 +1,34 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 4" + date="2022-06-03T01:40:17Z" + content=""" +FWIW indeed seems that all tests passed in reasonable time on smaug since I have added reporting of elapsed time: + +``` +(git)smaug:/mnt/datasets/datalad/ci/git-annex-ci-client-jobs[master]builds/2022 +$> git submodule foreach \"git grep '^Elapsed time: [0-9]' | grep smaug || :\" +Entering '02' +Entering '03' +Entering '04' +Entering '05' +result-smaug-700/handle-result.yaml-125-88838e79-success/result-smaug-700/git-annex.log:Elapsed time: 437 seconds +result-smaug-701/handle-result.yaml-127-0b187de0-success/result-smaug-701/git-annex.log:Elapsed time: 404 seconds +result-smaug-702/handle-result.yaml-129-d31f0988-success/result-smaug-702/git-annex.log:Elapsed time: 406 seconds +result-smaug-703/handle-result.yaml-131-92d8565a-success/result-smaug-703/git-annex.log:Elapsed time: 496 seconds +result-smaug-704/handle-result.yaml-133-25ffc5f5-success/result-smaug-704/git-annex.log:Elapsed time: 432 seconds +result-smaug-705/handle-result.yaml-135-8d90e5e7-success/result-smaug-705/git-annex.log:Elapsed time: 411 seconds +result-smaug-706/handle-result.yaml-137-b47dd77c-success/result-smaug-706/git-annex.log:Elapsed time: 427 seconds +result-smaug-707/handle-result.yaml-139-ee5bee3b-success/result-smaug-707/git-annex.log:Elapsed time: 563 seconds +result-smaug-709/handle-result.yaml-141-4dda2de6-success/result-smaug-709/git-annex.log:Elapsed time: 419 seconds +result-smaug-710/handle-result.yaml-143-7df269b8-success/result-smaug-710/git-annex.log:Elapsed time: 442 seconds +result-smaug-711/handle-result.yaml-145-206b0f6a-success/result-smaug-711/git-annex.log:Elapsed time: 414 seconds +result-smaug-712/handle-result.yaml-147-fc2e89a9-success/result-smaug-712/git-annex.log:Elapsed time: 577 seconds +result-smaug-713/handle-result.yaml-149-e633d635-success/result-smaug-713/git-annex.log:Elapsed time: 448 seconds +result-smaug-714/handle-result.yaml-151-5156c589-success/result-smaug-714/git-annex.log:Elapsed time: 429 seconds +Entering '06' +result-smaug-715/handle-result.yaml-153-daa2f773-success/result-smaug-715/git-annex.log:Elapsed time: 411 seconds +result-smaug-716/handle-result.yaml-155-5e82d554-success/result-smaug-716/git-annex.log:Elapsed time: 645 seconds +``` +"""]] From 6d00c1130775b605c4f66faad0be92572cc5f274 Mon Sep 17 00:00:00 2001 From: "war1025@f884a3422ae0f27c6a2eb2335b383c5098f01c92" Date: Fri, 3 Jun 2022 14:20:09 +0000 Subject: [PATCH 4/5] --- doc/forum/Change_annex_id_after_harddrive_clone.mdwn | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 doc/forum/Change_annex_id_after_harddrive_clone.mdwn diff --git a/doc/forum/Change_annex_id_after_harddrive_clone.mdwn b/doc/forum/Change_annex_id_after_harddrive_clone.mdwn new file mode 100644 index 0000000000..6cf1b03895 --- /dev/null +++ b/doc/forum/Change_annex_id_after_harddrive_clone.mdwn @@ -0,0 +1,5 @@ +I got a new laptop the other day. To set it up, I just cloned the home directory from my desktop. +As part of that, I have a git annex repository that now has all the content, but still thinks it is +my desktop. +What is the right way to convert it into a unique repository? +I changed the annex uuid in the config file, but I am not sure if that is correct or sufficient. From cbd82f768e588b206d0e4245f655fff3588ba006 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Fri, 3 Jun 2022 16:42:39 +0000 Subject: [PATCH 5/5] Added a comment --- ...ment_14_9f6fde051e877638a56094d3179dc550._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/get_is_busy_doing_nothing/comment_14_9f6fde051e877638a56094d3179dc550._comment diff --git a/doc/bugs/get_is_busy_doing_nothing/comment_14_9f6fde051e877638a56094d3179dc550._comment b/doc/bugs/get_is_busy_doing_nothing/comment_14_9f6fde051e877638a56094d3179dc550._comment new file mode 100644 index 0000000000..f50d8233bb --- /dev/null +++ b/doc/bugs/get_is_busy_doing_nothing/comment_14_9f6fde051e877638a56094d3179dc550._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 14" + date="2022-06-03T16:42:38Z" + content=""" +ok, none of those 3 jobs returned, I have a good number (>40) of git* related processes \"running\", see [screenshot](http://www.onerussian.com/tmp/git-annexes-stuck-1.png) . +I will keep it in this \"state\" for possible introspection for another hour, and if no immediate ideas on what to look at, I will kill/update git-annex (from that `10.20220322-g7b64dea`) and restart jobs. + +FWIW, I have git config annex.stalldetection 1KB/120s + +"""]]