From 2f32cc25894995c585e0426f5caf5f41bf9bd230 Mon Sep 17 00:00:00 2001
From: "robert.schuetz@7942237bf71a2ae4f5d3cb047d167612b8c9e311"
 <robertschuetz@web>
Date: Tue, 7 Nov 2017 12:45:43 +0000
Subject: [PATCH]

---
 ...ote_listed_in_whereis_but_not_in_info.mdwn | 29 +++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 doc/forum/Remote_listed_in_whereis_but_not_in_info.mdwn

diff --git a/doc/forum/Remote_listed_in_whereis_but_not_in_info.mdwn b/doc/forum/Remote_listed_in_whereis_but_not_in_info.mdwn
new file mode 100644
index 0000000000..ef7b2caac6
--- /dev/null
+++ b/doc/forum/Remote_listed_in_whereis_but_not_in_info.mdwn
@@ -0,0 +1,29 @@
+I came across the following strange behaviour:
+
+    $ git annex whereis "2013-WS/ecl/Algorithms for Scoring Coreference Chains.pdf"
+    whereis 2013-WS/ecl/Algorithms for Scoring Coreference Chains.pdf (4 copies) 
+      	    04140d86-2ad5-4807-a789-f478dbf477c7 -- [mojzesz]
+   	    622fce61-6702-448f-8eee-9a31d8a67e14 -- here
+   	    8bb266ed-453d-4489-9d8a-de38b2bc77c2
+   	    d8149441-8b4d-4d37-bed4-c0f709165f32 -- [alonzo]
+    ok
+
+I have no idea what that remote without a name is. Is there a way to find that out?
+
+Plus, it is not shown by
+
+    $ git annex info
+    repository mode: indirect
+    trusted repositories: 0
+    semitrusted repositories: 3
+	    04140d86-2ad5-4807-a789-f478dbf477c7 -- [mojzesz]
+ 	    622fce61-6702-448f-8eee-9a31d8a67e14 -- here
+ 	    d8149441-8b4d-4d37-bed4-c0f709165f32 -- [alonzo]
+    untrusted repositories: 4
+	    00000000-0000-0000-0000-000000000001 -- web
+ 	    00000000-0000-0000-0000-000000000002 -- bittorrent
+ 	    11d4b299-0170-49b3-8b71-7ea2c47f212b -- nexus5
+ 	    dd22c018-65f8-4fa7-b880-48616016e272 -- miracle
+    ...
+
+Also, is there a way to mark that remote as dead?