# Disk space problem for ELK stack running in an azure VM

**URL:** <https://discuss.elastic.co/t/disk-space-problem-for-elk-stack-running-in-an-azure-vm/247330>\
**Category:** Elasticsearch\
**Created:** [September 3, 2020, 6:17am UTC](https://discuss.elastic.co/t/disk-space-problem-for-elk-stack-running-in-an-azure-vm/247330 "2020-09-03T06:17:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rowshan\_Sathi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rowshan_sathi/32/73371_2.png) [@Rowshan\_Sathi](https://discuss.elastic.co/u/Rowshan_Sathi)\
**Post date:** [September 3, 2020, 6:17am UTC](https://discuss.elastic.co/t/disk-space-problem-for-elk-stack-running-in-an-azure-vm/247330/1 "2020-09-03T06:17:51Z")

</div>

Hi,  
I have installed ELK stack on Azure VM. The details of my system-  
Ubuntu 18.04  
ELasticsearch- 7.8.1

I have configured curator script and runing it every morning and also I am clearing logs according to its size but still I see that the disk size is increasing. here is the disk current condition:  
Filesystem Size Used Avail Use% Mounted on  
udev 3.9G 0 3.9G 0% /dev  
tmpfs 794M 712K 793M 1% /run  
**/dev/sdb1 29G 24G 5.9G 80% /**  
tmpfs 3.9G 0 3.9G 0% /dev/shm  
tmpfs 5.0M 0 5.0M 0% /run/lock  
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup  
/dev/sdb15 105M 3.6M 101M 4% /boot/efi  
/dev/sda1 16G 45M 15G 1% /mnt  
tmpfs 794M 0 794M 0% /run/user/1000

So ultimately clearing index logs does not helping to decrease the disk size here  
/dev/sdb1 29G 24G 5.9G 80% /

any suggestion please.

---

<div class="post-metadata">

**Author:** ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)\
**Post date:** [September 4, 2020, 12:50am UTC](https://discuss.elastic.co/t/disk-space-problem-for-elk-stack-running-in-an-azure-vm/247330/2 "2020-09-04T00:50:03Z")

</div>

`/dev/sdb1` is the temp disk on Azure VMs, mounted on `/mnt` on Ubuntu.

Be mindful that this disk is ephemeral in nature and not persistent; A VM can be moved to a different host at **any** point in time for various reasons, including hardware failures. When this happens, the VM will be created on the new host using the OS disk from the storage account, and **new temp storage will be created on the new host** , so you will lose any data on that disk.

Since you're using Elasticsearch 7.8.1, take a look at [Index Lifecycle Management (ILM) for managing indices](https://www.elastic.co/guide/en/elasticsearch/reference/7.8/getting-started-index-lifecycle-management.html). You can [create a lifecycle policy to delete older indices](https://www.elastic.co/guide/en/elasticsearch/reference/7.8/ilm-delete.html). I don't know if this will solve the problem you're having, but it may work better for deleting older indices than using curator.

---

<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:** [October 2, 2020, 12:52am UTC](https://discuss.elastic.co/t/disk-space-problem-for-elk-stack-running-in-an-azure-vm/247330/4 "2020-10-02T00:52:44Z")

</div>

Closed on October 2, 2020, 12:52am UTC

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