Confirmation sensitive command

I need to purge the rclone cache as the system disk has been filled up with it.

Can you confirm whether the correct command to do that is:

rclone --cache-db-purge

or

rclone --cache-db-purge lsd cache:test

both are cited in the thread here:

I'm a bit confused and I cannot get this wrong

Also, when I do:

root@PC-IT-UBUIEX:~# rclone lsd cache:test

I get:

2021/07/02 13:01:04 Failed to create file system for "cache:test": didn't find section in config file

is this normal?

hello,

as per the documentation,
"The queue and the temporary storage is persistent across restarts but can be cleared on startup with the --cache-db-purge flag."

you need to replace cache with the name of the remote you want to purge.
to see the name of your remotes, do rclone listremotes

the cache remote has been depreciated and has known bugs that will never get fixed.
https://rclone.org/cache/#status

Thanks. One question, if I only want to empty the local cache (not anything else, just to free enough space on the system disk that I can have autocomplete back), can you confirm whether I can just do:

rclone --cache-db-purge

?

i have never used the cache.
it never left beta, has too many bugs and now we have the vfs cache

if you want to empty the local cache at startup, you run rclone --cache-db-purge

sorry, not understanding what the else is?

Ah, bah I use Beta too (sorry I should have said that at the onset):

root@PC-IT-UBUIEX:~# rclone -V
rclone v1.56.0-beta.5550.3349b055f
- os/version: ubuntu 18.04 (64 bit)
- os/kernel: 4.15.0-144-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.16.5
- go/linking: static
- go/tags: none

meanwhile (probably you know already):

root@PC-IT-UBUIEX:~# rclone --cache-db-purge
Usage:
  rclone [flags]
  rclone [command]

Available Commands:
  about           Get quota information from the remote.
  authorize       Remote authorization.
  backend         Run a backend specific command.
  cat             Concatenates any files and sends them to stdout.

sorry, not understanding what the else is?

I'm not trying to use rclone per, I only want to empty the cache so I can do something on that machine,

as i wrote above, you need to tell rclone what remote cache to purge.
rclone remote: --cache-db-purge change remote:`, to whatever remote cache you want to purge.

thanks for your answer. And what if I want to purge the cache on the local machine (the source)?

You run the command on the same machine that the cache is. The cache is stored locally on the same machine. It's not stored on the remote.

guys, thank you all for the help and sorry for being daft, but I type "the command" on the same machine, and I get (I put it above but here is it so you don't have to scroll up):

root@PC-IT-UBUIEX:~# rclone --cache-db-purge
Usage:
  rclone [flags]
  rclone [command]

Available Commands:
  about           Get quota information from the remote.
  authorize       Remote authorization.
  backend         Run a backend specific command.
  cat             Concatenates any files and sends them to stdout.
  check           Checks the files in the source and destination match.

Again, you need to pass the remote name.

Ok, so I did:

rclone blbz: --cache-db-purge 

blbz: is one of the remote I used on that machine (there is a dozen remotes, should I do it for all of them?)

and I get:

root@PC-IT-UBUIEX:~# rclone blbz: --cache-db-purge 
Error: unknown command "blbz:" for "rclone"
Run 'rclone --help' for usage.
You could use 'rclone selfupdate' to get latest features.

2021/07/02 17:03:02 Fatal error: unknown command "blbz:" for "rclone"

Right, you need to pass a command, something.

rclone lsd blbz: --cache-db-purge

When you started this post, there was a template that you deleted that collects all the info so we help answer things quickly instead of going back and forth. That's why it says please read etc.

ok, thanks. It took me a while (sorry and thanks for your patience) but the penny did drop.

Have a nice week end!

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