From 924e89f932dc65972c58f47483ec09525558a480 Mon Sep 17 00:00:00 2001
From: Ilya_Shlyakhter <Ilya_Shlyakhter@web>
Date: Tue, 23 Jul 2019 20:56:19 +0000
Subject: [PATCH] added bug report about fsck flagging dead keys as errors

---
 ...nnex-fsck_reports_dead_keys_as_errors.mdwn | 53 +++++++++++++++++++
 1 file changed, 53 insertions(+)
 create mode 100644 doc/bugs/git-annex-fsck_reports_dead_keys_as_errors.mdwn

diff --git a/doc/bugs/git-annex-fsck_reports_dead_keys_as_errors.mdwn b/doc/bugs/git-annex-fsck_reports_dead_keys_as_errors.mdwn
new file mode 100644
index 0000000000..6bbc7532a5
--- /dev/null
+++ b/doc/bugs/git-annex-fsck_reports_dead_keys_as_errors.mdwn
@@ -0,0 +1,53 @@
+### Please describe the problem.
+
+[[git-annex-fsck]] flags as an error a key that has zero copies, even after the key has been marked dead with [[git-annex-dead]] .
+
+### What steps will reproduce the problem?
+
+see below
+
+### What version of git-annex are you using? On what operating system?
+[[!format sh """
+(master_env_v149_py36) 16:48  [viral-ngs-benchmarks] $ git annex version
+git-annex version: 7.20190708-gbc74eb1
+build flags: Assistant Webapp Pairing S3 WebDAV Inotify DBus DesktopNotify TorrentParser MagicMime Feeds Testsuite
+dependency versions: aws-0.21.1 bloomfilter-2.0.1.0 cryptonite-0.25 DAV-1.3.3 feed-1.0.1.0 ghc-8.4.2 http-client-0.5.14 persistent-sql\
+ite-2.9.2 torrent-10000.1.1 uuid-1.3.13 yesod-1.6.0
+key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_2\
+24 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 BLAKE2B256E BLAKE2B256 BLAKE2B512E BLAKE2B512 BLAKE2B160E BLAKE2B160 BLAKE\
+2B224E BLAKE2B224 BLAKE2B384E BLAKE2B384 BLAKE2S256E BLAKE2S256 BLAKE2S160E BLAKE2S160 BLAKE2S224E BLAKE2S224 BLAKE2SP256E BLAKE2SP256\
+ BLAKE2SP224E BLAKE2SP224 SHA1E SHA1 MD5E MD5 WORM URL
+remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav adb tahoe glacier ddar hook external
+operating system: linux x86_64
+supported repository versions: 5 7
+upgrade supported from repository versions: 0 1 2 3 4 5 6
+local repository version: 5
+(master_env_v149_py36) 16:51  [viral-ngs-benchmarks] $ uname -a
+Linux ip-172-31-87-151.ec2.internal 4.14.133-113.105.amzn2.x86_64 #1 SMP Wed Jul 10 16:57:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
+(master_env_v149_py36) 16:51  [viral-ngs-benchmarks] $
+"""]]
+
+### Please provide any additional information below.
+
+[[!format sh """
+
+(master_env_v149_py36) 16:48  [viral-ngs-benchmarks] $ git annex dead --key MD5E-s363253--e5190755e0ded033bff6b5184adc2fb2.pkl.gz
+dead MD5E-s363253--e5190755e0ded033bff6b5184adc2fb2.pkl.gz ok
+(master_env_v149_py36) 16:48  [viral-ngs-benchmarks] $ echo $?
+0
+(master_env_v149_py36) 16:48  [viral-ngs-benchmarks] $ git annex fsck --key MD5E-s363253--e5190755e0ded033bff6b5184adc2fb2.pkl.gz
+fsck MD5E-s363253--e5190755e0ded033bff6b5184adc2fb2.pkl.gz
+  ** No known copies exist of MD5E-s363253--e5190755e0ded033bff6b5184adc2fb2.pkl.gz
+  These dead repositories used to have copies
+        fb0aac49-5cdd-41ce-9d3b-101d9a91d623 -- crogit runner crogrun_190718_135857_6024
+
+  (Avoid this check by running: git annex dead --key )
+failed
+(recording state in git...)
+git-annex: fsck: 1 failed
+
+"""]]
+
+### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
+git-annex helps me keep my sanity :)  
+