It's possible that the bug is with the mount and not with the check , or maybe it's the interplay between the two.
Looking at the last line in the log I see this:
2025/04/20 18:53:44 DEBUG : d/RI/3KWTSV6HS3KSHD2K6G42L5S7GSNXD7: forgetting directory cache
Which makes me wonder if it's a dupe of this issue:
What is the problem you are having with rclone?
The remote B2 storage that I've mounted with rclone mount works great for a period of time, but then experiences a deadlock where any process interacting with that filesystem goes into an uninterruptible state. (e.g., if I try to cp a file to it, the command doesn't succeed, and a Ctrl-C will not kill the process.).
This deadlock is absolutely affected by the --dir-cache-time option. When running with the default, the deadlock occurs about 5 minu…
Here are the full DEBUG logs this time. You can see most of the logs have the encrypted filenames which are the cryptomator files it's reading via the mount: