Just as the title says. Files written to the cache are not handled by the "Automatically protect new and modified files" feature when they are moved to disk.
This is because, when the Unraid Mover runs, a partial file is created on the disk. After the move is complete, this file.partial is then moved to the original file name on the disk. Therefore, inotifywait does not see the move as a close_write, but rather a moved_to.
I have tested and fixed this on my dev server. PR inbound.
Just as the title says. Files written to the cache are not handled by the "Automatically protect new and modified files" feature when they are moved to disk.
This is because, when the Unraid Mover runs, a partial file is created on the disk. After the move is complete, this file.partial is then moved to the original file name on the disk. Therefore, inotifywait does not see the move as a close_write, but rather a moved_to.
I have tested and fixed this on my dev server. PR inbound.