# Metricbeat with AWS EFS

**URL:** <https://discuss.elastic.co/t/metricbeat-with-aws-efs/75950>\
**Category:** Beats\
**Created:** [February 21, 2017, 8:01pm UTC](https://discuss.elastic.co/t/metricbeat-with-aws-efs/75950 "2017-02-21T20:01:41Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [February 22, 2017, 1:40am UTC](https://discuss.elastic.co/t/metricbeat-with-aws-efs/75950/2 "2017-02-22T01:40:29Z")

</div>

I'm curious what `stat -f` and `df` show for that EFS volume?

This is kind of similar to [Failed to parse [system.filesystem.files]: Numeric value (18446744073709551615) out of range of long](https://discuss.elastic.co/t/failed-to-parse-system-filesystem-files-numeric-value-18446744073709551615-out-of-range-of-long/66860) but in this case it's for a huge filesystem instead of a invalid value. So I think we need to come up with some way to handle this.

---

_[View the full topic](https://discuss.elastic.co/t/metricbeat-with-aws-efs/75950)._