# Separated filesystems for data and logs?

**URL:** <https://discuss.elastic.co/t/separated-filesystems-for-data-and-logs/252686>\
**Category:** Elasticsearch\
**Created:** [October 20, 2020, 12:56pm UTC](https://discuss.elastic.co/t/separated-filesystems-for-data-and-logs/252686 "2020-10-20T12:56:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ffknob](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ffknob/32/37008_2.png) [@ffknob](https://discuss.elastic.co/u/ffknob)\
**Post date:** [October 20, 2020, 12:56pm UTC](https://discuss.elastic.co/t/separated-filesystems-for-data-and-logs/252686/1 "2020-10-20T12:56:29Z")

</div>

Hi,

I'd like to know your thoughts on the best/recommended approach to organize the filesystem of a VM that will run an Elasticsearch instance.

How should I separate things in such a way for the service to have some degree od resilience if, let's say, the logs fill an entire disk?

I guess on first approach would be to separate "data" and "logs" in different partitions, so I can grow then separatedly...

So, what is the recommended filesystem configuration for a production ready Elasticsearch node?

Thank you

---

<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:** [November 17, 2020, 12:56pm UTC](https://discuss.elastic.co/t/separated-filesystems-for-data-and-logs/252686/2 "2020-11-17T12:56:33Z")

</div>

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