# Elasticsearch - solving \`No space left on device\`

**URL:** <https://discuss.elastic.co/t/elasticsearch-solving-no-space-left-on-device/299838>\
**Category:** Elasticsearch\
**Created:** [March 16, 2022, 8:34am UTC](https://discuss.elastic.co/t/elasticsearch-solving-no-space-left-on-device/299838 "2022-03-16T08:34:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sokolmateusz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sokolmateusz/32/103058_2.png) [@sokolmateusz](https://discuss.elastic.co/u/sokolmateusz)\
**Post date:** [March 16, 2022, 8:34am UTC](https://discuss.elastic.co/t/elasticsearch-solving-no-space-left-on-device/299838/1 "2022-03-16T08:34:34Z")

</div>

Hi!  
I'm using ELK (Elasticsearch, kibana, filebeat, metricbeat) deployed via Helm.  
I'm collecting small amount logs from a few containers and PVC for Elasticsearch is set to 2Gi.  
For some reason this space after one night gets filled and kibana isn't able to show any logs and `k logs elasticsearch-master-0` shows:

```auto
Caused by: java.io.IOException: No space left on device

```

in the stack trace. And those PV are filled +95%. After one day to make my stack work I have to clean PVC and restart deployment.

How can I solve/debug this issue? What is actually being stored there so quickly? Is there an option for yaml configuration to make elasticstack drop the oldest content of it's storage to avoid this issue and make ELK stack run for longer time?

Thank you for any guidance and tips.

---

<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:** [April 13, 2022, 8:34am UTC](https://discuss.elastic.co/t/elasticsearch-solving-no-space-left-on-device/299838/2 "2022-04-13T08:34:52Z")

</div>

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