# Data directory on remort serever

**URL:** <https://discuss.elastic.co/t/data-directory-on-remort-serever/264972>\
**Category:** Elasticsearch\
**Created:** [February 21, 2021, 4:17am UTC](https://discuss.elastic.co/t/data-directory-on-remort-serever/264972 "2021-02-21T04:17:16Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 21, 2021, 6:43pm UTC](https://discuss.elastic.co/t/data-directory-on-remort-serever/264972/4 "2021-02-21T18:43:31Z")

</div>

Have a look at:

> [@Why NFS is to be avoided for data directories](https://discuss.elastic.co/t/why-nfs-is-to-be-avoided-for-data-directories/215240):
>
> ES: 7.5 I have seen the recommendations in official documentation to 'avoid NFS' when using them as data directories for elasticsearch. I have also seen almost everywhere in the forums to 'avoid NFS' but couldn't find a proper explanation. Is it due to the fact that NFS is exported as a file system, and not a block device? Since there would be higher number of concurrent writes and reads, NFS would have protocol level bottlenecks. Is it due to network latency related issues of any network…

---

_[View the full topic](https://discuss.elastic.co/t/data-directory-on-remort-serever/264972)._