I'm considering using RClone as a backup destination and have a question about the VFS Caching layer.
I get that if I want full file operation support I need to use write caching, and it's not a problem while some file is being worked with.
However, the asynchronous nature of file writeback (i.e. - file could be uploaded long after the app that created it already closed) means that any error is not propagated out to an app, that is working with a file. This is not very convenient in my case, because even if my backup software/script reports that all is done, there might be some upload failures later. Which is a data loss, that could not be caught immediately.
Any way to make RClone initiate upload right when file is closed and don't report success back until upload is complete, similar to what happens on delete?
That way I could (at the cost of some performance) ensure data consistency, and an error could propagate out to an app, so that it could decide what to do with it (log, do its own retry, alert or whatever).
Actually, this is something that RClone kinda does with
--vfs-cache-mode off - if there is an error, app gets to know that there was one. But it's not an option for me.
--vfs-write-back 0s doesn't work for me either (and might even have a bug, still trying to pin it down before reporting).
Any suggestions? If there is no way of doing this, should I make feature request on GitHub?