Oh "rclone copy" apparently doesn't force a sync to disk. And if you're running it a server with e.g. 512GB of RAM than this can result in a ":wq" in vim to appear as if it froze.

Is vim forcing a generic sync to disk when it exists? Or is this some kind of kernel bug that it doesn't just force that one file to sync to disk and instead waits for everything currently pending to be written?
What's going on here exactly?!?

#vim #rclone #linux #lvm

(I come to this suspicion as running a "sync; vim foo.txt" and immediately inserting some text and ":wq!"-ing causes vim to behave normally as well as the sync before it even starts to take multiple minutes)
(Btw, we're almost at 10 minutes by now for it to "sync" this time...)