We are using Logstash to ingest our logs and we are facing some issues due inodes being reused. We tried all possible options on Logstash side so we are exploring the OS side.
As far as I can see, if I create a file, drop it and later on I create a new one, most of the time it will get the same inode
[root@XXXX~]# touch a.txt
[root@XXXX~]# stat -c%i a.txt
671092802
[root@XXXX~]# rm a.txt
rm: remove regular empty file ‘a.txt’? y
[root@XXXX~]# touch a.txt
[root@XXXX~]# stat -c%i a.txt
671092802
[root@XXXX~]# rm a.txt
rm: remove regular empty file ‘a.txt’? y
[root@XXXX~]# touch b.txt
[root@XXXX~]# stat -c%i b.txt
671092802
How can I prevent OS with XFS to reuse recently used inodes for new files?
Ideally, we would like to define a period of time between the file is deleted until the inode is being reused. The disk is big so we don't expect issue reaching inode limits.
Thanks
Asked by sickfear
(3 rep)
Dec 7, 2021, 11:40 AM
Last activity: Dec 7, 2021, 01:14 PM
Last activity: Dec 7, 2021, 01:14 PM