It should not throw errors when you use a quota policy which isn't supported
Some of the other policies?
Perhaps someone could translate @Animosity022's mergerfs setup into an equivalent setup for the union backend? That would make a good thing to test and a good cookbook example.
Looking forward to this! Seems very similar to mergerfs which I'm using which is good. I have a question about cache-time - can you expand a bit on what this does please?
Cache time just controls the time for which the free space of the remote is cached, nothing else. So when you are using a policy which needs to know the free space, instead of reading it for every transaction it reads it from the cache which makes things more efficient at a cost of a bit of accuracy.
How does rclone union treat mix of ro/rw? i.e. will there be CoW?
I'm currently using unionfs to pool a local folder (RW) + a rclone remote (RO).
So when any change is done to the RO remote, a copy is saved on the local folder before any modification is applied i.e. unionfs CoW.
This serves as a form of protection against cryptovirus and accidental changes since any change will only be updated to the remote when I manually run an upload / cleanup script.
Upload a edited file to union should be ok since it would choose a writable upstream. However if only the metadata is being updated, SetModTime/Update would be used. In this case, no upstream would be chosen unless we want to re-upload a file to a writable upstream.
Just tried to unify 4 onedrive remotes, works perfectly fine for me.
@ncw, One question though: If Rclone fails to upload the object into the first remote for some reason, does it automatically try upload on the second remote?
rclone will do the retries it normally does (--low-level retries if possible) but if those fail then I don't think it will try the next remote. Is that right @Max-Sum
I never used mergerfs, but after reading the docs, I assumed if I use lfs, Rclone will try to fill the storage on the first remote, if the first remote has no storage left or the file is larger than available storage, then it will try to store the file on second remote and so on and so forth. Am I wrong?
So, basically I wants to fill the first remote as much as possible, then try second and so on and so forth.
Update: I was wrong, Rclone did not try to put the file on second remote, when first remote was full. I guess a fail-over function must needed.