# \[BUG\] Incorrect disk usage statistics

**URL:** <https://discuss.elastic.co/t/bug-incorrect-disk-usage-statistics/103207>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [October 9, 2017, 9:57am UTC](https://discuss.elastic.co/t/bug-incorrect-disk-usage-statistics/103207 "2017-10-09T09:57:26Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [November 1, 2017, 8:06pm UTC](https://discuss.elastic.co/t/bug-incorrect-disk-usage-statistics/103207/4 "2017-11-01T20:06:18Z")

</div>

I think I looked into this before and found that Metricbeat does not factor in the `available` value reported by statfs when it does its calculations. [Filesystem pct/used not same as reported by df](https://discuss.elastic.co/t/filesystem-pct-used-not-same-as-reported-by-df/71795/8?u=andrewkroh)

So you think we should change the calculation in the Metricbeat code? If so we should also check the Windows code to see if it has a similar problem.

---

_[View the full topic](https://discuss.elastic.co/t/bug-incorrect-disk-usage-statistics/103207)._