New files manually uploaded to IDrive e2 by copy-pasting them using file explorer (rclone mount) are counting twice in storage space because an old version is being generated too, despite being a file that didn't exist.
If I use iDrive e2 website (webapp) to upload, this issue doesn't happen, so it's related to rclone.
I want versioning, but there's no reason to exist two versions for a file was never modified. Think of big untouched media files, I can't waste using double the space nor should I need to run cleanup all the time.
Run the command 'rclone version' and share the full output of the command.
Then here you are. It let me believe that problem is your files browser - maybe it uses some staged copy operation etc. If cp works than clearly it is not mount issue.
Sure it is your call. But if you use mount for write operations than without VFS level >= "write" you will experience many surprises - there are plenty of posts on this forum related to it. Simply a lot of programs assume that they write to well behaved POSIX filesystem - and mount without cache is very far from it. It is ok to use VFS = off for read only but for writes it is lottery.
I used to use cache, but I had a feel it drains my drives lifespan unnecessarily. So I use tmpfs and was placing cache there, but then I was unable to upload files larger than the available space in tmp because it needs to make a copy in cache before uploading... Not sure if all of this makes sense, but that's basically why I avoid using cache. I'd like to be wrong if VFS fixes this Dolphin issue.
Difficult to comment as I do not know your workload but SSD drives in most cases last much longer than people think. I am heavy user I think and I use 1% of drive writes per year. Even if I used 5% than drive would last 20 years... I stopped paying any attention to this.
You can test it easily.
Here another example (there are many) where some programs get confused when writing to uncached mount:
Without any cache you have to carefully test your software and e.g. in your case stop using this particular file browser - or try to fix it with its authors.
I just tried and --vfs-cache-max-size didn't have any effect, a file larger than the max size was copied to cache folder. So it would still fail if there's no enough space for the copy in cache folder.
So for giant files I guess I should avoid pasting by file manager and use rclone copy instead.