# Elastic disk stats not correct with Kubernetes local storage **URL:** \ **Category:** Elasticsearch\ **Tags:** docker\ **Created:** [July 30, 2019, 5:46pm UTC](https://discuss.elastic.co/t/elastic-disk-stats-not-correct-with-kubernetes-local-storage/192956 "2019-07-30T17:46:53Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![data\_smith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/data_smith/32/124122_2.png) [@data\_smith](https://discuss.elastic.co/u/data_smith)\ **Post date:** [July 30, 2019, 5:46pm UTC](https://discuss.elastic.co/t/elastic-disk-stats-not-correct-with-kubernetes-local-storage/192956/1 "2019-07-30T17:46:53Z")
I'm running Elasticsearch in a Docker container in Kubernetes with local storage. Elastic only sees an overlay mount, which is at the root. It doesn't see the local storage mount. And so it's not reporting the correct amount of storage available and it's causing issues with shard allocation and watermark alerting. Has anyone else run into this issue? ``` Filesystem Type Size Mounted on overlay overlay 500G / /dev/disk-disk xfs 2T /data ``` Elastic only sees the overlay and therefore only sees 500G as opposed to 2T ---
**Author:** ![data\_smith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/data_smith/32/124122_2.png) [@data\_smith](https://discuss.elastic.co/u/data_smith)\ **Post date:** [July 30, 2019, 8:07pm UTC](https://discuss.elastic.co/t/elastic-disk-stats-not-correct-with-kubernetes-local-storage/192956/2 "2019-07-30T20:07:00Z")
Nevermind. I need to set my /data path. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 27, 2019, 8:17pm UTC](https://discuss.elastic.co/t/elastic-disk-stats-not-correct-with-kubernetes-local-storage/192956/3 "2019-08-27T20:17:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.