# Disk space full, addition of a new disk and data folder path in elasticsearch.yml does not start ES

**URL:** <https://discuss.elastic.co/t/disk-space-full-addition-of-a-new-disk-and-data-folder-path-in-elasticsearch-yml-does-not-start-es/105117>\
**Category:** Elasticsearch\
**Created:** [October 24, 2017, 7:05pm UTC](https://discuss.elastic.co/t/disk-space-full-addition-of-a-new-disk-and-data-folder-path-in-elasticsearch-yml-does-not-start-es/105117 "2017-10-24T19:05:35Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![shivalkarrahul](https://avatars.discourse-cdn.com/v4/letter/s/e79b87/32.png) [@shivalkarrahul](https://discuss.elastic.co/u/shivalkarrahul)\
**Post date:** [October 24, 2017, 7:05pm UTC](https://discuss.elastic.co/t/disk-space-full-addition-of-a-new-disk-and-data-folder-path-in-elasticsearch-yml-does-not-start-es/105117/1 "2017-10-24T19:05:35Z")

</div>

Elasticsearch version (bin/elasticsearch --version): 2.1.11

JVM version (java -version): 1.8.0\_91

OS version (uname -a if on a Unix-like system): SLES 11 SP4

Description of the problem including expected versus actual behavior:  
I have ElasticSearch up and running with data folder path in elasticsearch.yml (data.path) and suddenly the disk space goes out of memory, adding another disk and its path in elasticsearch.yml (data.path) does not help to start elasticsearch and it gives the error .  
Second data folder path is detected by ES but it does not write data in the second path which it should as disk one is out of space

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 24, 2017, 7:41pm UTC](https://discuss.elastic.co/t/disk-space-full-addition-of-a-new-disk-and-data-folder-path-in-elasticsearch-yml-does-not-start-es/105117/2 "2017-10-24T19:41:48Z")

</div>

There is no 2.1.16 release, you may want to check that.

> [@shivalkarrahul](#):
>
> Second data folder path is detected by ES but it does not write data in the second path which it should as disk one is out of space

Elasticsearch doesn't handle it like that. You will need to make sure there is space on the first device.

---

<div class="post-metadata">

**Author:** ![shivalkarrahul](https://avatars.discourse-cdn.com/v4/letter/s/e79b87/32.png) [@shivalkarrahul](https://discuss.elastic.co/u/shivalkarrahul)\
**Post date:** [October 24, 2017, 7:48pm UTC](https://discuss.elastic.co/t/disk-space-full-addition-of-a-new-disk-and-data-folder-path-in-elasticsearch-yml-does-not-start-es/105117/3 "2017-10-24T19:48:11Z")

</div>

Even if we have some space on the first device, soon it will go out of space. What we need is to have data on the old disk and write new data on the second disk

---

<div class="post-metadata">

**Author:** ![shivalkarrahul](https://avatars.discourse-cdn.com/v4/letter/s/e79b87/32.png) [@shivalkarrahul](https://discuss.elastic.co/u/shivalkarrahul)\
**Post date:** [October 24, 2017, 7:49pm UTC](https://discuss.elastic.co/t/disk-space-full-addition-of-a-new-disk-and-data-folder-path-in-elasticsearch-yml-does-not-start-es/105117/4 "2017-10-24T19:49:16Z")

</div>

> [@warkolm](#):
>
> There is no 2.1.16 release, you may want to check that.

Sorry, 2.1.1

---

<div class="post-metadata">

**Author:** ![shivalkarrahul](https://avatars.discourse-cdn.com/v4/letter/s/e79b87/32.png) [@shivalkarrahul](https://discuss.elastic.co/u/shivalkarrahul)\
**Post date:** [October 24, 2017, 7:54pm UTC](https://discuss.elastic.co/t/disk-space-full-addition-of-a-new-disk-and-data-folder-path-in-elasticsearch-yml-does-not-start-es/105117/5 "2017-10-24T19:54:46Z")

</div>

If we give one Data-Folder path in elasticsearch.yml (path.data: [/opt/drive1/data]),start ES, perform write operations and disk space goes out of memory, we add another path in elasticsearch.yml (path.data: [/opt/drive1/data, /opt/drive2/data]) and start ES, ES picks up the second path and creates its base folders but does not write any data in the second path and no folders of shards can be seen in the second path.

So you mean to say, we can not have data at multiple locations at later point of time.?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [October 24, 2017, 8:31pm UTC](https://discuss.elastic.co/t/disk-space-full-addition-of-a-new-disk-and-data-folder-path-in-elasticsearch-yml-does-not-start-es/105117/6 "2017-10-24T20:31:18Z")

</div>

The way Elasticsearch wrote to multiple paths in 2.X was not as ideal as it could be. We made improvements to it in 5.X.

There's really no easy way to recover other than make more disk space on the first drive.

---

<div class="post-metadata">

**Author:** ![shivalkarrahul](https://avatars.discourse-cdn.com/v4/letter/s/e79b87/32.png) [@shivalkarrahul](https://discuss.elastic.co/u/shivalkarrahul)\
**Post date:** [October 24, 2017, 8:35pm UTC](https://discuss.elastic.co/t/disk-space-full-addition-of-a-new-disk-and-data-folder-path-in-elasticsearch-yml-does-not-start-es/105117/7 "2017-10-24T20:35:43Z")

</div>

Thank you so much.

---

<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 21, 2017, 8:35pm UTC](https://discuss.elastic.co/t/disk-space-full-addition-of-a-new-disk-and-data-folder-path-in-elasticsearch-yml-does-not-start-es/105117/8 "2017-11-21T20:35:57Z")

</div>

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