Confirmed now only delay on the second open
The negative effect can often be reduced by also adding something like: --vfs-cache-max-age=7d --vfs-cache-max-size=10G
Perhaps we should add little mount quick start in the beginning of the mount doc to share a good all-round setups for Windows, Mac and Other (Linux). This is my current suggestion for a simple all-round Windows mount with 10GB free for caching:
rclone mount --network-mode --buffer-size=0 --vfs-cache-mode=full --vfs-cache-max-age=7d --vfs-cache-max-size=10G
Yes, but not recommended.
That is possible, but again not recommended. Most wouldn't understand the risks/consequences nor how to mitigate them. It would therefore easily make the rclone cache a great place to hide malware and thereby increase the risk of rclone being considered malware too.
Well spotted!
Perhaps we can improve responsiveness by doing an open/close immediately after the first close - or something along these lines. Then it will often not be noticeable. That may well be easier said that done.
I naively tried a RDWR open/close immediately after the truncate and that was instant, but it didn't have the desired effect - perhaps Defender is sniffing the file header to see it is an executable.