[scrypt]
type = crypt
remote = scache:
filename_encryption = standard
directory_name_encryption = true
password = superpass1
password2 = superpass2
I do mount with
rclone mount scrypt: /mnt/sdrive --fast-list --allow-other --buffer-size 0 --dir-cache-time 72h --cache-info-age 96h --timeout 1h &
Mount shows up in /mnt/sdrive, files are accessible and all seems to work. But when i use "rclone lsd scrypt:" i always get the following error:
ERROR : /mnt/myhome/rclone/cache-backend/scache.db: Error opening storage cache. Is there another rclone running on the same remote? failed to open a cache connection to "/mnt/myhome/.cache/rclone/cache-backend/scache.db": timeout
I checked with "ps -ef | grep rclone" and there is no other process for this mount running. I got another remote mounted (another gdrive, with diff client id), but that is named differently (gcrypt2:)
What am i doing wrong? What is needed to get a correct working cache backend? I do not get an error when using "rclone lsd sdrive:" but i just want to make sure a i got a working cloud -> cache -> crypt setup. Thanks in advance.
"It's telling you that you already have a rclone process running with the cache backend as only one process can access it."
Well, there is, but for a completely different remote drive. Even when i start rclone with a different user, i get the same error on lsd.
"Is there a reason you want to use the cache backend? I personally would not and just mount the crypt."
I did some tests with vfs and wasnt that happy, so i decided to give the cache backend a try. Why do you think its not needed? Isnt it faster to do so?
Not sure what that means as the error says you are trying to run a second cache rclone process on the same remote. I can only report what the error is as you'd want to check what you have running.
It's not needed and it's faster without it generally. There are some edge use cases where it may make sense.
UserBBB did rclone lsd scrypt: and got the error i described. Maybe i am missunderstanding something here, but it is only one mount process running for the mentioned remotes.
For the cache backend, there is only one process that ever can be running for a remote at one time. If you get the error, you have a process running still.
Me again, i did a mistake earlier (had no cache in config) - but it is still not working. I already deleted everything, wiped google drive and started from scratch including new credentials/project. Tested on 3 different machines, same error occours everytime.
As Animosity mentioned above, you cannot run a separate rclone ls scrypt: while the mount for scrypt is running as only one rclone process can access the cache db at a time.