Please can someone advise as to the appropriate cache / memory configuration options for my use case? I want to make my 'OneDrive:/Scanned Documents' folder available using rclone on my router. It has 512MB ram.
So at the moment I have:
rclone mount "OneDrive:/Scanned Documents/" /tmp/OneDrive/ --cache-dir /tmp --vfs-cache-mode full --vfs-cache-max-size 10M --buffer-size 10M --uma
sk 000 --allow-other
Thanks. So download seems OK, but if I upload a large file it just goes at full rate and eats up all my router RAM. What controls the memory usage here? I want the upload cache to be 1-10MBs.
When writing to a rclone mount, the behaviour appears to be that file is saved in storage, and then once the file is saved in storage rclone begins to upload it. Is it possible instead to have rclone upload as the file is written to the rclone mount directory?
BTW I am using:
root@OpenWrt:/etc/init.d# rclone version
rclone v1.52.2_2020-06-24
So what about those who want to be able to upload files larger than they have storage space for? Is there a way to avoid being limited to uploading files < storage space on device on which rclone is run on?
In my case I am keen to set it so that it does not cache on upload. Or better limit the cache to 10MB for upload. Is that possible? But setting 'vfs-cache-mode off' results in a copy in Windows failing. Otherwise setting cache to 10MB as I thought I did above results in the entire 200MB file transferring very quickly (but I only have 2-3Mbyte/s upload rate), then hang. Then file transfer completes.
root@OpenWrt:/tmp# rclone mount "OneDrive:/Scanned Documents/" /tmp/OneDrive/ --cache-dir /tmp --vfs-cache-mode off --buffer-size 10M --umask 000 --allow-other
2021/09/11 16:35:44 ERROR : SCAN_20210614_100214_001547.zip: WriteFileHandle: Truncate: Can't change size without --vfs-cache-mode >= writes
2021/09/11 16:35:45 ERROR : SCAN_20210614_100214_001547.zip: WriteFileHandle.Write: can't seek in file without --vfs-cache-mode >= writes
2021/09/11 16:35:46 ERROR : SCAN_20210614_100214_001547.zip: WriteFileHandle.Write: can't seek in file without --vfs-cache-mode >= writes
2021/09/11 16:35:47 ERROR : SCAN_20210614_100214_001547.zip: WriteFileHandle.Write: can't seek in file without --vfs-cache-mode >= writes
2021/09/11 16:35:48 ERROR : SCAN_20210614_100214_001547.zip: WriteFileHandle.Write: can't seek in file without --vfs-cache-mode >= writes
2021/09/11 16:35:49 ERROR : SCAN_20210614_100214_001547.zip: WriteFileHandle.Write: can't seek in file without --vfs-cache-mode >= writes
2021/09/11 16:35:50 ERROR : SCAN_20210614_100214_001547.zip: WriteFileHandle.Write: can't seek in file without --vfs-cache-mode >= writes
2021/09/11 16:35:51 ERROR : SCAN_20210614_100214_001547.zip: WriteFileHandle.Write: can't seek in file without --vfs-cache-mode >= writes
2021/09/11 16:35:52 ERROR : SCAN_20210614_100214_001547.zip: WriteFileHandle.Write: can't seek in file without --vfs-cache-mode >= writes
2021/09/11 16:35:53 ERROR : SCAN_20210614_100214_001547.zip: WriteFileHandle.Write: can't seek in file without --vfs-cache-mode >= writes
Thank you so much for your continued input here. Actually I am only needing to upload PDFs of around 20MB from my scanner. For that purpose is simply only:
But for completeness is there no way to have this mount upload mechanism facilitate uploads of files with sizes greater than the available storage on the device from which rclone is run? In other words chunk is written to mount, rclone uploads chunk, and repeat? Rather than entire file uploaded, then rclone uploads entire file.
Does my init.d script below seem reasonable to you? The reason for mount in /tmp is to avoid writing to the router non-volatile memory. The reason for the 'mkdir' is because /tmp is reset on router reboot. Is the rclone mount as daemon and stop using 'fusermount -zu' OK? I have the script arranged to start before samba start and to stop before samba stop.
I'm using rclone to backup my cloud accounts for one year. It was crashed on 128MB router with OpenWRT, but on 512 MB it's ok.
Some settings from my scripts: