Clean the inode cache, which should remove the inode from
memory, and when it's needed again, it's initialized with
i_readcount zero.
$ echo 2 | sudo tee /proc/sys/vm/drop_caches
This may happen indirectly from time to time on systems,
as part of normal memory cleansing/reclaiming, and thus
the problem might be avoided or never noticed.
This might impact performance, as the inode and dentry
caches are flushed.
Workaround:
---
Clean the inode cache, which should remove the inode from
memory, and when it's needed again, it's initialized with
i_readcount zero.
$ echo 2 | sudo tee /proc/sys/ vm/drop_ caches
This may happen indirectly from time to time on systems, reclaiming, and thus
as part of normal memory cleansing/
the problem might be avoided or never noticed.
This might impact performance, as the inode and dentry
caches are flushed.