Can You Refresh a Mounted Remote Without Polling?

I've provided all information below as the category requires it, but I don't particularly have an issue. The Dropbox remote type doesn't currently support polling (per the GitHub issue below). Is there any way to manually refresh the mount contents without restarting the remote? Apologies if this is addressed somewhere, I was unable to find it mentioned anywhere.

What is the problem you are having with rclone?

The Dropbox remote type does not support polling.

What is your rclone version (output from rclone version)

rclone v1.53.3
- os/arch: linux/amd64
- go version: go1.15.5

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Linux (Debian 10), 64 bit.

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


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

rclone mount dropbox:/ /mnt/remote/dropbox --allow-other --log-level INFO --log-file "/mnt/remote/dropbox.log" --user-agent="RandomString" --uid 1001 --gid 1001 --dir-cache-time 1000h --poll-interval 15s --umask 002 --cache-dir="/mnt/remote/cache/dropbox" --vfs-cache-mode full --vfs-cache-max-size 20G --vfs-cache-max-age 48h --fast-list --daemon

The rclone config contents with secrets removed.

type = dropbox
token = {"access_token":""}

type = crypt
remote = dropboxraw:/path/
filename_encryption = standard
directory_name_encryption = true
password = pwd
password2 = slt


add --rc to the mount command

and do this to refresh the mount
rclone rc vfs/refresh recursive=true

whenever i want jellyfin to scan media on the mount, i run that command first.


Thank you so much! I had no idea that refreshing VFS would actually refresh the content too :smiley: Really appreciate how quick your reply was, sorry for not replying back myself sooner!

sure, glad to help

by the way,
--fast-list does nothing on a mount.

1 Like

You don't have to run rc, you can also kill -HUP the rclone process and it'll forgot the cache as well.

felix     788780  788568  1 19:34 pts/0    00:00:00 rclone mount gcrypt: /home/felix/test -vv
felix     788990  788951  0 19:34 pts/1    00:00:00 grep --color=auto rclone
felix@gemini:~$ kill -HUP 788780


felix@gemini:~$ rclone mount gcrypt: /home/felix/test -vv
2021/02/09 19:34:31 DEBUG : rclone: Version "v1.54.0" starting with parameters ["rclone" "mount" "gcrypt:" "/home/felix/test" "-vv"]
2021/02/09 19:34:31 DEBUG : Creating backend with remote "gcrypt:"
2021/02/09 19:34:31 DEBUG : Using config file from "/opt/rclone/rclone.conf"
2021/02/09 19:34:31 DEBUG : Creating backend with remote "GD:crypt"
2021/02/09 19:34:32 DEBUG : Encrypted drive 'gcrypt:': Mounting on "/home/felix/test"
2021/02/09 19:34:32 DEBUG : : Root:
2021/02/09 19:34:32 DEBUG : : >Root: node=/, err=<nil>
2021/02/09 19:34:42 DEBUG : : forgetting directory cache

But that'll kill the mount, right? Meaning once the mount was setup again, Docker containers would need to be restarted to see the new mount. I just need polling, which rc seems to solve the issue of.

No, it just refreshes the directory cache.

I have the output above, you can see it.

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