# Taking snapshot doubled disk usage

**URL:** <https://discuss.elastic.co/t/taking-snapshot-doubled-disk-usage/49098>\
**Category:** Elasticsearch\
**Created:** [May 3, 2016, 7:40pm UTC](https://discuss.elastic.co/t/taking-snapshot-doubled-disk-usage/49098 "2016-05-03T19:40:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Raynor](https://avatars.discourse-cdn.com/v4/letter/r/6de8d8/32.png) [@Raynor](https://discuss.elastic.co/u/Raynor)\
**Post date:** [May 3, 2016, 7:40pm UTC](https://discuss.elastic.co/t/taking-snapshot-doubled-disk-usage/49098/1 "2016-05-03T19:40:16Z")

</div>

Hi all,

I run into a problem that we are running out of disk when taking a snapshot of the cluster. Taking snapshot actually doubled the fleet disk space.

We are using ElasticSearch 1.7.1 with Elasticsearch-cloud-aws as the plugin to upload snapshot to S3.

Has anyone run into this problem yet? Thanks!

---

<div class="post-metadata">

**Author:** ![Raynor](https://avatars.discourse-cdn.com/v4/letter/r/6de8d8/32.png) [@Raynor](https://discuss.elastic.co/u/Raynor)\
**Post date:** [May 3, 2016, 9:06pm UTC](https://discuss.elastic.co/t/taking-snapshot-doubled-disk-usage/49098/2 "2016-05-03T21:06:54Z")

</div>

Turns out we turned on DEBUG which logs all the data 😛

---

<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:** [July 5, 2017, 10:54pm UTC](https://discuss.elastic.co/t/taking-snapshot-doubled-disk-usage/49098/3 "2017-07-05T22:54:15Z")

</div>