From affeccdb65c995c9fac0adfec84a966b5c63734e Mon Sep 17 00:00:00 2001 From: "beryllium@5bc3c32eb8156390f96e363e4ba38976567425ec" Date: Tue, 27 Feb 2024 02:23:34 +0000 Subject: [PATCH] --- ..._unused_on_directory_special_remote__63__.mdwn | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/git-annex_unused_on_directory_special_remote__63__.mdwn diff --git a/doc/forum/git-annex_unused_on_directory_special_remote__63__.mdwn b/doc/forum/git-annex_unused_on_directory_special_remote__63__.mdwn new file mode 100644 index 0000000000..41956fa361 --- /dev/null +++ b/doc/forum/git-annex_unused_on_directory_special_remote__63__.mdwn @@ -0,0 +1,15 @@ +Should git-annex unused work on a directory special remote? I tried the following: + + $ git-annex unused --from SanDisk64GB4Torrented + unused SanDisk64GB4Torrented (checking for unused data...) ok + $ + +However, despite git-annex list --in SanDisk64GB4Torrented demonstrating that there were no annex files in it, the size of the directory was still large. And I can see a file in tmp/ of that annex's directory: + + $ ls tmp/ + SHA256E-s2351316992--bdfba5df0bd72cffdb398fe885d9e36d052617647c0ae4fd0579a8fc785c95ba.iso + $ + +Am I right to think that the file being present in tmp/ should cause git-annex unused to list it? + +I'm assuming it's fine to just remove the file. But I guess this might be a bug... so I'm putting it out there just in case.