Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File Integrity Plugin - Files Moved from the Cache to Disk Are Not Handled By "Automatically protect new and modified files" #78

Open
Torqu3Wr3nch opened this issue May 3, 2023 · 0 comments

Comments

@Torqu3Wr3nch
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant