Rclone-spool folders in temp fill up entire system drive

What is the problem you are having with rclone?

rclone-spool folders in %Temp% fill up entire harddrive

What is your rclone version (output from rclone version)


Which cloud storage system are you using? (eg Google Drive)

Google Drive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone serve ftp "JottaCrypt:" --addr :21 --user admin --pass admin
rclone mount "JottaFTP:" J:

-vfs-cache-max* commands seem to do nothing. Any ideas?
Don't think this happened in earlier rclone versions from 1-2 years ago.
Using with NSSM (run as service). My hard drive is constantly full.
These rclone-spool folders seem to be cache with actual files.
Why is it ignoring --vfs-cache-max-size etc (have tested with those)?

This is an unfortunate interaction between jotta and the mount command.

In short Jotta can't upload unknown length files, but the mount (without VFS cache) doesn't know how big the files are when they are opened. This means they have to be spooled to disk.

You can set the TMPDIR environment variable to point to somewhere where you have more space.

You need to set --vfs-cache-mode writes for that to have an effect and that is another solution - probably the best one, use --vfs-cache-mode writes and limit the size of the directory with --vfs-cache-max-size

Thanks for the help, though it still fills up 660GB on the harddrive with this:

serve ftp "JottaCrypt:" --addr :21 --user admin --pass admin --vfs-cache-mode writes  --vfs-cache-max-size 100G

Even if I set it to my 8TB drive, I'm pretty sure it would fill up that too.

You'd have to share a log file with the settings so we can see what's going on.

Run the command with -vv and share the log file.

How big are the biggest files you are uploading? These need to be stored entirely on the disk first.

According to WinDirStat some of the biggest files are close to 100GB. I think I will try to disable intro marker generation etc in Plex to see if that helps. I suspect it is trying to analyse all these files at once with a library scan making the cache too big.

The logfile would show what's going on....

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.