# Multiple path.data configuration work strangely on ES2.4.1

**URL:** <https://discuss.elastic.co/t/multiple-path-data-configuration-work-strangely-on-es2-4-1/74179>\
**Category:** Elasticsearch\
**Created:** [February 7, 2017, 8:30am UTC](https://discuss.elastic.co/t/multiple-path-data-configuration-work-strangely-on-es2-4-1/74179 "2017-02-07T08:30:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![caixiac](https://avatars.discourse-cdn.com/v4/letter/c/a4c791/32.png) [@caixiac](https://discuss.elastic.co/u/caixiac)\
**Post date:** [February 7, 2017, 8:30am UTC](https://discuss.elastic.co/t/multiple-path-data-configuration-work-strangely-on-es2-4-1/74179/1 "2017-02-07T08:30:30Z")

</div>

I have the following path.data configuration in elasticsearch.yml:

path.data: /appdata/data,/var/lib/data

While /appdata is on vdb with 1G size and /var/lib/data is on vda with 2G size.  
The issue is when /var/lib/data has used 100%, /appdata usage is always less than 1% and  
elsticseach reports no space available on disk. Shouldn't it write data on /appdata/ directory  
instead of complaining this?

BTW total VDA disk size is 20G, but we only allocated 2G to /var

Thanks&Regards.

Caixia

---

<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:30am UTC](https://discuss.elastic.co/t/multiple-path-data-configuration-work-strangely-on-es2-4-1/74179/2 "2017-03-07T08:30:36Z")

</div>

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