# Elastic Search disk/storage usage identification
**URL:** https://discuss.elastic.co/t/elastic-search-disk-storage-usage-identification/163282
**Category:** Elasticsearch
**Created:** [January 7, 2019, 11:34pm UTC](https://discuss.elastic.co/t/elastic-search-disk-storage-usage-identification/163282 "2019-01-07T23:34:57Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@naveengauba](https://discuss.elastic.co/u/naveengauba)
#### Post date: [January 7, 2019, 11:34pm UTC](https://discuss.elastic.co/t/elastic-search-disk-storage-usage-identification/163282/1 "2019-01-07T23:34:57Z")
Hi All
I am running Elastic Search 6.2.4 on a 150 GB virtual machine. The disk is 31% utilized which means more than 100 GB is free.
df -k .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/centos-root 157260800 47396716 109864084 31% /
I keep seeing these messages on the elastic search logs files.
[2019-01-07T14:59:58,596][INFO][o.e.c.r.a.DiskThresholdMonitor] [JUz2YCv] low disk watermark [85%] exceeded on [JUz2YCvyRxi-qrtqrO3Z0A][JUz2YCv][/var/lib/elasticsearch/nodes/0] free: 5.2gb[10.5%], replicas will not be assigned to this node
I have not done any specific cluster settings in Elastic Search.
GET /\_cluster/settings
{
"persistent": {},
"transient": {}
}
Could someone help me why I am seeing this issue?
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [January 8, 2019, 8:55am UTC](https://discuss.elastic.co/t/elastic-search-disk-storage-usage-identification/163282/2 "2019-01-08T08:55:45Z")
Can you share your `elasticsearch.yml` config file?
Also, can you share the whole output of `df` (i.e. without the `.` at the end)?
---
### Author:  [@naveengauba](https://discuss.elastic.co/u/naveengauba)
#### Post date: [January 8, 2019, 10:41pm UTC](https://discuss.elastic.co/t/elastic-search-disk-storage-usage-identification/163282/3 "2019-01-08T22:41:43Z")
hi David
Thanks for the pointer. Once I saw the whole output of "df" I noticed that I was looking at the wrong mount. The mount that was being used by ES data folders was indeed having space issues. This is no longer an issue now. And can be closed.
thanks..Naveen
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 5, 2019, 10:41pm UTC](https://discuss.elastic.co/t/elastic-search-disk-storage-usage-identification/163282/4 "2019-02-05T22:41:46Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.