From 3d1d77a1bb3d403f2ec870f7a0dde5ca82d1e89a Mon Sep 17 00:00:00 2001 From: "kirrik96@419b50c9fb455c2f172184be932c5df3635a3cf4" Date: Tue, 18 Apr 2023 21:12:21 +0000 Subject: [PATCH] --- ...ut_why_file_is_not_being_auto-dropped.mdwn | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/forum/Finding_out_why_file_is_not_being_auto-dropped.mdwn diff --git a/doc/forum/Finding_out_why_file_is_not_being_auto-dropped.mdwn b/doc/forum/Finding_out_why_file_is_not_being_auto-dropped.mdwn new file mode 100644 index 0000000000..3354d5d27e --- /dev/null +++ b/doc/forum/Finding_out_why_file_is_not_being_auto-dropped.mdwn @@ -0,0 +1,22 @@ +Hello! + +I've being using git-annex for a while, and I currently have a file which is not being auto dropped, although it has enough of copies. +I also cannot find out which commit introduced it. + +```sh +% git annex whereis --key=SHA256E-s1611030508--280877e3adf28838f631f0e3ffd892e1bc04842528a1ffa8d8d23711974d2d08.mp4 +whereis SHA256E-s1611030508--280877e3adf28838f631f0e3ffd892e1bc04842528a1ffa8d8d23711974d2d08.mp4 (3 copies) + 0155e17e-5a25-4be0-b344-6f37d6e37b8c -- [remote1] + 2f439291-b8ea-4726-83a7-827b3caf8700 -- user@pc:~/repo [here] + 831a8460-73d4-4684-bd5d-02433590b3bc -- [remote2] +ok + +% git annex numcopies +2 +``` + +`git annex drop --auto` doesn't seem to help safely deleting it. + +I tried searching the hash with `% git log -S ""`, but it returns nothing. + +Why could this be, and how do I find and drop this files (and how to treat them in general)?