Hello guys
What is the problem you are having with rclone?
I have been working on a project to have rClone as a cloud storage solution with BOX.
It successfully worked for all expected results except the last one: I want to simulate a file modification on the server that is actually wrong (and by configuration uploaded to BOX): then I would use versioning in BOX to restore a previous correct version.
While versioning works perfectly from rClone on Server > BOX, it does not work from BOX > rClone mount.
What I tested (waited 10min even though command shall update in 60s)
- Waited 10 minutes ==> file in rClone mount NOT updated
- Deleted "wrong" file in /TMP_BOX/vfs/... and waited 10 min ==> file in rClone mount NOT updated
- Restarted server with rClone command above ==> ==> file in rClone mount WAS updated
What is your rclone version (output from rclone version)
rclone v1.54.1
- os/arch: linux/amd64
- go version: go1.15.8
Which OS you are using and how many bits (eg Windows 7, 64 bit)
CentOS Linux release 7.9.2009 (Core) - 64 bit
Which cloud storage system are you using? (eg Google Drive)
BOX
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone mount BOX:"folder_in_box" /mnt/box
--daemon
--vfs-cache-mode full
--vfs-cache-max-size 30G
--vfs-write-back 10s
--vfs-cache-max-age 72h
--vfs-cache-poll-interval 60s
--poll-interval 60s
--network-mode
--cache-dir /TMP_BOX
--vfs-case-insensitive
--vfs-read-chunk-size 64M
--ignore-errors
--ignore-case-sync
--write-back-cache
--allow-non-empty
--no-modtime
The rclone config contents with secrets removed.
[BOX]
type = box
box_sub_type = user
token = {"access_token":"token_goes_here","token_type":"bearer","refresh_token":"refresh_goes_here","expiry":"2021-08-10T11:53:55.990294975+08:00"}