# Old file with new name found

**URL:** <https://discuss.elastic.co/t/old-file-with-new-name-found/41766>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 15, 2016, 11:08am UTC](https://discuss.elastic.co/t/old-file-with-new-name-found/41766 "2016-02-15T11:08:00Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![jstangroome](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jstangroome/32/8654_2.png) [@jstangroome](https://discuss.elastic.co/u/jstangroome)\
**Post date:** [March 30, 2016, 10:31pm UTC](https://discuss.elastic.co/t/old-file-with-new-name-found/41766/18 "2016-03-30T22:31:26Z")

</div>

Hi,

I was also hoping it had been fixed but there is still an edge case apparently. Should I re-open issue 1010 or would you like to handle this another way?

You may also like to review a similar issue I've reproduced:

> [@Filebeat 1.1.2 does not record correct inode values of rotated logs on exit](https://discuss.elastic.co/t/filebeat-1-1-2-does-not-record-correct-inode-values-of-rotated-logs-on-exit/45749):
>
> Hi, I am seeing filebeat re-ship rotated log files when the filebeat service restarts. I have created a basic configuration and bash script which starts filebeat, writes to a log file, rotates it a couple of times (with pauses in between to allow filebeat to notice) and then stops filebeat. Link at the end. After filebeat stops, the registry has persisted the wrong inodes for the log files present on disk. As such, when filebeat starts again, an existing log file will appear to be a new file …

Regards,

Jason

---

_[View the full topic](https://discuss.elastic.co/t/old-file-with-new-name-found/41766)._