# Underlying file changed by an external force

**URL:** https://discuss.elastic.co/t/underlying-file-changed-by-an-external-force/137555
**Category:** Elasticsearch
**Created:** [June 27, 2018, 7:36am UTC](https://discuss.elastic.co/t/underlying-file-changed-by-an-external-force/137555 "2018-06-27T07:36:32Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [June 27, 2018, 1:47pm UTC](https://discuss.elastic.co/t/underlying-file-changed-by-an-external-force/137555/4 "2018-06-27T13:47:40Z")

</div>

> [@xiaomage](#):
>
> glusterfs is used to a filesystem to store the elasticsearch data

The first two Google hits for `elasticsearch glusterfs` lead to two serious-looking open GlusterFS issues that Elasticsearch triggers:

[https://bugzilla.redhat.com/show\_bug.cgi?id=1390050](https://bugzilla.redhat.com/show_bug.cgi?id=1390050)  
[https://bugzilla.redhat.com/show\_bug.cgi?id=1379568](https://bugzilla.redhat.com/show_bug.cgi?id=1379568)

This may be one of them, or may be something else, but it seems worth rethinking your setup.

> [@xiaomage](#):
>
> issue caused by different timezone, am i right?

I don't think so. Both of the times I quoted are in UTC (note the trailing `Z`) and differ by 28 seconds, so it seems unlikely to be a timezone issue.

---

_[View the full topic](https://discuss.elastic.co/t/underlying-file-changed-by-an-external-force/137555)._