# Nfs filesystem: DirectoryIteratorException No error information

**URL:** <https://discuss.elastic.co/t/nfs-filesystem-directoryiteratorexception-no-error-information/195596>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [August 17, 2019, 1:47pm UTC](https://discuss.elastic.co/t/nfs-filesystem-directoryiteratorexception-no-error-information/195596 "2019-08-17T13:47:59Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![hsarkar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hsarkar/32/20914_2.png) [@hsarkar](https://discuss.elastic.co/u/hsarkar)\
**Post date:** [August 17, 2019, 1:48pm UTC](https://discuss.elastic.co/t/nfs-filesystem-directoryiteratorexception-no-error-information/195596/1 "2019-08-17T13:48:00Z")

</div>

I am running a 3 node elasticsearch cluster with the following configuration  
Version: 6.5.4  
Environment: Docker  
Xmx = 3.75  
Filesystem type: nfs  
Replication: 1

I am getting following error in stdout logs. [[pastebin](https://pastebin.com/7jFg8kM7)], adding few lines below for quick readability.  
The error started coming on all 3 nodes, Size of data directory being 22.8G, 29.8G, 22.4G on the 3 nodes respectively.

```
[2019-08-17T01:25:03,582][WARN][o.e.i.c.IndicesClusterStateService] [spotlight-es-0-athena-18] [[audits][2]] marking and sending shard failed due to [shard failure, reason [corrupt [11/1106]
Caused by: org.apache.lucene.index.CorruptIndexException: Hit unexpected exception while reading segment infos (resource=commit(null))
Caused by: java.nio.file.DirectoryIteratorException: java.nio.file.FileSystemException: /usr/share/elasticsearch/data/nodes/0/indices/J0ltYZOfSs-SW5N7gPoo1Q/2/index: No error information
Caused by: java.nio.file.FileSystemException: /usr/share/elasticsearch/data/nodes/0/indices/J0ltYZOfSs-SW5N7gPoo1Q/2/index: No error information

```

How do I debug this further? Can it be because of nfs filesystem used as index storage?

---

<div class="post-metadata">

**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\
**Post date:** [August 17, 2019, 6:49pm UTC](https://discuss.elastic.co/t/nfs-filesystem-directoryiteratorexception-no-error-information/195596/2 "2019-08-17T18:49:17Z")

</div>

> [@hsarkar](#):
>
> Can it be because of nfs filesystem used as index storage?

Yes. Elasticsearch does not supports NFS filesystem.

---

<div class="post-metadata">

**Author:** ![hsarkar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hsarkar/32/20914_2.png) [@hsarkar](https://discuss.elastic.co/u/hsarkar)\
**Post date:** [August 18, 2019, 5:00am UTC](https://discuss.elastic.co/t/nfs-filesystem-directoryiteratorexception-no-error-information/195596/3 "2019-08-18T05:00:33Z")

</div>

Why is this a WARN and not an error? All the 3 nodes are printing the same stacktrace.

---

<div class="post-metadata">

**Author:** ![thiago](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thiago/32/32096_2.png) [@thiago](https://discuss.elastic.co/u/thiago)\
**Post date:** [August 18, 2019, 11:01am UTC](https://discuss.elastic.co/t/nfs-filesystem-directoryiteratorexception-no-error-information/195596/4 "2019-08-18T11:01:43Z")

</div>

Probably because it is the replica that is failing, not the primary shard.

---

<div class="post-metadata">

**Author:** ![hsarkar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hsarkar/32/20914_2.png) [@hsarkar](https://discuss.elastic.co/u/hsarkar)\
**Post date:** [August 20, 2019, 12:34pm UTC](https://discuss.elastic.co/t/nfs-filesystem-directoryiteratorexception-no-error-information/195596/5 "2019-08-20T12:34:30Z")

</div>

I see that makes sense. Thanks a lot Thiago.

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [August 26, 2019, 2:11pm UTC](https://discuss.elastic.co/t/nfs-filesystem-directoryiteratorexception-no-error-information/195596/6 "2019-08-26T14:11:58Z")

</div>

Elasticsearch doesn't treat any shard failure as an error whether it's the primary or a replica, because there will normally be another copy of the shard elsewhere to take over. It's something you might want to investigate, but doesn't need immediate action, so a `WARN` makes more sense than an `ERROR`.

---

<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:** [September 23, 2019, 2:12pm UTC](https://discuss.elastic.co/t/nfs-filesystem-directoryiteratorexception-no-error-information/195596/7 "2019-09-23T14:12:05Z")

</div>

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