# Logstash 7.9.1 have issues in ARM **URL:** \ **Category:** Logstash\ **Created:** [September 23, 2020, 1:04am UTC](https://discuss.elastic.co/t/logstash-7-9-1-have-issues-in-arm/249596 "2020-09-23T01:04:00Z")\ **Posts on this page:** 1\ **Showing post:** 9
**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:** [September 25, 2020, 3:46pm UTC](https://discuss.elastic.co/t/logstash-7-9-1-have-issues-in-arm/249596/9 "2020-09-25T15:46:57Z")
> [@goutham968](#): > > Is it possible to disable the sincedb functionality ? No. The in-memory sincedb is always maintained. You can set ``` sincedb_path => "/dev/null" ``` but it will still write the in-memory db to /dev/null, and it may still choose to use the atomic write for that. In that case it would chown /dev/null If I were you I would try pointing sincedb\_path at every file system you have available, and see if one of them chooses the non-atomic write. Local disk, RAM disk, NFS mount, /dev/null... I see you are on aarch64. A user had the [same problem](https://discuss.elastic.co/t/issue-with-logstash-on-aarch64/133008) a couple of years ago. No solution was found. I am wondering if .blockdev? is broken in the ruby implementation. --- _[View the full topic](https://discuss.elastic.co/t/logstash-7-9-1-have-issues-in-arm/249596)._