(wkfhlkwhflkh4lk isn't matching anything) also all removed empty folders are checked or fixed!
msg:error: Error stating dir '/mount/2TBlast/test_deleteme'. No such file or directory.
dir_error:d6:test_deleteme: Dir stat error
(the above is for test_deleteme which was removed since last sync and it is for check, if fix is used the folder will be recovered).
This happens no matter if the path is absolute or relative, no matter if the pattern is matching an existing file or nothing from the array.
By the way maybe there should be a warning when the filter doesn't match anything that the absolute paths actually refers to the path "inside the array". I know it is something documented but the usage is a bit unusual and "fix" is not something that users do often (I hope...) and they might get caught and think their data isn't there.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When running a check or fix with something like
snapraid -v -l /tmp/test -f wkfhlkwhflkh4lk check
(wkfhlkwhflkh4lk isn't matching anything) also all removed empty folders are checked or fixed!
msg:error: Error stating dir '/mount/2TBlast/test_deleteme'. No such file or directory.
dir_error:d6:test_deleteme: Dir stat error
(the above is for test_deleteme which was removed since last sync and it is for check, if fix is used the folder will be recovered).
This happens no matter if the path is absolute or relative, no matter if the pattern is matching an existing file or nothing from the array.
By the way maybe there should be a warning when the filter doesn't match anything that the absolute paths actually refers to the path "inside the array". I know it is something documented but the usage is a bit unusual and "fix" is not something that users do often (I hope...) and they might get caught and think their data isn't there.
I checked both with 10 stable and last 11 beta, it is the same.
Hi John,
Thanks for reporting. Going to fix that.
Ciao,
Andrea