# Elasticsearch does not see indices stored on filesystem

**URL:** <https://discuss.elastic.co/t/elasticsearch-does-not-see-indices-stored-on-filesystem/74175>\
**Category:** Elasticsearch\
**Created:** [February 7, 2017, 8:15am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-see-indices-stored-on-filesystem/74175 "2017-02-07T08:15:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ygokirmak](https://avatars.discourse-cdn.com/v4/letter/y/d07c76/32.png) [@ygokirmak](https://discuss.elastic.co/u/ygokirmak)\
**Post date:** [February 7, 2017, 8:15am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-see-indices-stored-on-filesystem/74175/1 "2017-02-07T08:15:39Z")

</div>

Hi all  
I have a 2 node elasticsearch cluster for log analysis and reporting,  
yesterday I had some disk problem and had to restart nodes,  
now the problem is although there are indices persisted on filesystem, I can not see old indices before restart via elasticsearch

Indices that are on filesystem

> drwxrwxr-x 8 ntp docker 4096 Jan 17 15:36 zipkin-2017-01-17  
> drwxrwxr-x 8 ntp docker 4096 Jan 18 03:00 zipkin-2017-01-18  
> drwxrwxr-x 8 ntp docker 4096 Jan 19 03:00 zipkin-2017-01-19  
> drwxrwxr-x 8 ntp docker 4096 Jan 20 03:00 zipkin-2017-01-20  
> drwxrwxr-x 8 ntp docker 4096 Jan 21 03:00 zipkin-2017-01-21  
> drwxrwxr-x 8 ntp docker 4096 Jan 22 03:00 zipkin-2017-01-22  
> drwxrwxr-x 8 ntp docker 4096 Jan 23 03:00 zipkin-2017-01-23  
> drwxrwxr-x 8 ntp docker 4096 Jan 24 03:00 zipkin-2017-01-24  
> drwxrwxr-x 8 ntp docker 4096 Jan 25 03:00 zipkin-2017-01-25  
> drwxrwxr-x 8 ntp docker 4096 Jan 26 03:00 zipkin-2017-01-26  
> drwxrwxr-x 8 ntp docker 4096 Jan 27 03:00 zipkin-2017-01-27  
> drwxrwxr-x 8 ntp docker 4096 Jan 28 03:00 zipkin-2017-01-28  
> drwxrwxr-x 8 ntp docker 4096 Jan 29 03:00 zipkin-2017-01-29  
> drwxrwxr-x 8 ntp docker 4096 Jan 30 03:00 zipkin-2017-01-30  
> drwxrwxr-x 8 ntp docker 4096 Jan 31 03:00 zipkin-2017-01-31  
> drwxrwxr-x 8 ntp docker 4096 Feb 1 03:00 zipkin-2017-02-01  
> drwxrwxr-x 8 ntp docker 4096 Feb 2 03:00 zipkin-2017-02-02  
> drwxrwxr-x 8 ntp docker 4096 Feb 3 03:00 zipkin-2017-02-03  
> drwxrwxr-x 8 ntp docker 4096 Feb 4 03:00 zipkin-2017-02-04  
> drwxrwxr-x 8 ntp docker 4096 Feb 5 03:00 zipkin-2017-02-05  
> drwxrwxr-x 8 ntp docker 4096 Feb 6 03:00 zipkin-2017-02-06

Indices returned from curl

> $ curl '[http://xx.xx.xx.xx:9200/\_cat/indices](http://xx.xx.xx.xx:9200/_cat/indices)' green open .kibana 5 1 43 1 226.3kb 113.1kb  
> green open zipkin-2017-02-07 5 1 8527 0 2.6mb 1.3mb

Where does elastic maintains its list of indices?  
How can I recover this data?

> {  
> "name" : "Ghost Rider",  
> "cluster\_name" : "xxx",  
> "version" : {  
> "number" : "2.4.0",  
> "build\_hash" : "xxx",  
> "build\_timestamp" : "2016-08-29T09:14:17Z",  
> "build\_snapshot" : false,  
> "lucene\_version" : "5.5.2"  
> },  
> "tagline" : "You Know, for Search"  
> }

thanks

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 7, 2017, 8:15am UTC](https://discuss.elastic.co/t/elasticsearch-does-not-see-indices-stored-on-filesystem/74175/2 "2017-03-07T08:15:50Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.