When listing problematic files, we should exclude storages where the id starts with "shared::xxx".
These are federated shares and the indexed files are located on a remote server, which itself might also have invalid mtimes, that we can't fix automatically.
Instead of reporting these and confusing admins who run it, skips them.
@artonge
When listing problematic files, we should exclude storages where the id starts with "shared::xxx".
These are federated shares and the indexed files are located on a remote server, which itself might also have invalid mtimes, that we can't fix automatically.
Instead of reporting these and confusing admins who run it, skips them.
@artonge