# Bug for sincedb with gz file

**URL:** https://discuss.elastic.co/t/bug-for-sincedb-with-gz-file/305602
**Category:** Logstash
**Created:** [May 25, 2022, 11:56am UTC](https://discuss.elastic.co/t/bug-for-sincedb-with-gz-file/305602 "2022-05-25T11:56:43Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [May 25, 2022, 1:01pm UTC](https://discuss.elastic.co/t/bug-for-sincedb-with-gz-file/305602/3 "2022-05-25T13:01:30Z")

</div>

> [@INS](#):
>
> Only last one line has a fully name of file and then after parsing the file it disappears.

Why do you care about the filename? The sincedb tracks files using the inode and device numbers. If a file is renamed from foo.log to foo.log.1 these do not change, so the input will know not to re-read it just because it has been rotated. There are [issues](https://discuss.elastic.co/t/how-logstash-works-for-10-000-lines-of-log-file/275118/4) with the sincedb, but I do not think this is one of them.

---

_[View the full topic](https://discuss.elastic.co/t/bug-for-sincedb-with-gz-file/305602)._
