From 89ac4e68bb8211f273db582e23775ccbcfe076e9 Mon Sep 17 00:00:00 2001 From: Lukey Date: Thu, 31 Dec 2020 21:46:33 +0000 Subject: [PATCH] Added a comment --- ...mment_7_96147f452229d09d4fa8ed4d606341aa._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/how_to_get_into_git_annex.../comment_7_96147f452229d09d4fa8ed4d606341aa._comment diff --git a/doc/forum/how_to_get_into_git_annex.../comment_7_96147f452229d09d4fa8ed4d606341aa._comment b/doc/forum/how_to_get_into_git_annex.../comment_7_96147f452229d09d4fa8ed4d606341aa._comment new file mode 100644 index 0000000000..f266af8de6 --- /dev/null +++ b/doc/forum/how_to_get_into_git_annex.../comment_7_96147f452229d09d4fa8ed4d606341aa._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="Lukey" + avatar="http://cdn.libravatar.org/avatar/c7c08e2efd29c692cc017c4a4ca3406b" + subject="comment 7" + date="2020-12-31T21:46:33Z" + content=""" +Hmm, you seem to have mixed a lot of things up here:
+1. You are not supposed to use `git annex unannex` to unlock a file. Just pretend this command doesn't exist for now and use `git annex unlock` instead. In general, look at the manpages of the commands. For example `man git-annex-unannex`.
+2. Before doing anything further, clean up your repository from the mistake above. First, add all unannexed files back to the annex with `git annex add .` (from the root of your repo) and then commit everything with `git annex sync`. `git status` should now output `nothing to commit, working tree clean`.
+3. After setting `git config annex.thin true` you are supposed to run `git annex fix`. That's exactly what the link you gave says. But as you are using btrfs, I suggest you not to use hard-links, as git annex makes use of reflinks already.
+4. Now that you have a clean worktree, try `git annex unused` again. If it still doesn't work post the full output of `git annex unused` here. +"""]] -- 2.30.2