Rclone mount takes exactly 1 minute to mount successfully

Help and Support
1

STOP and READ USE THIS TEMPLATE NO EXCEPTIONS - By not using this, you waste your time, our time and really hate puppies. Please remove these two lines and that will confirm you have read them.

What is the problem you are having with rclone?

rclone mount takes exactly 1 minute to mount successfully. Is this the expected behavior? whereas other mounters like s3fs mount within few seconds (5-10 secs)
Note - tried to mount a fresh cos bucket with no existing data in it.

Run the command 'rclone version' and share the full output of the command.

sh-5.1# rclone version
rclone v1.70.3-DEV

  • os/version: redhat 4.18 (64 bit)
  • os/kernel: 5.14.0-427.79.1.el9_4.x86_64 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.23.12
  • go/linking: dynamic
  • go/tags: none

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

IBM Cloud and IBM cloud object storage bucket.

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

```sh-5.1# rclone mount ibmcos:bha-coreos /root/tmp/bha --allow-other=true --config=/var/lib/coscsi-config/3d80b31facb6cd6e3f0b4d94b161e706a88be32c7aa5d70faf66f398456c998c/rclone.conf --daemon=true --log-file=/var/log/rclone.log --vfs-cache-mode=writes --log-level DEBUG```

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

```
sh-5.1# cat /var/lib/coscsi-config/3d80b31facb6cd6e3f0b4d94b161e706a88be32c7aa5d70faf66f398456c998c/rclone.conf
[ibmcos]
type = s3
endpoint = https://s3.direct.us-south.cloud-object-storage.appdomain.cloud
provider = IBMCOS
env_auth = true
access_key_id = xxx
secret_access_key = xxx
location_constraint = us-south-standard
bucket_acl=private
max_upload_parts=64
upload_concurrency=30
memory_pool_flush_time=30s
acl=private
upload_cutoff=256Mi
chunk_size=64Mi
copy_cutoff=1Gi
disable_checksum=true
low_level_retries=3
```

A log from the command that you were trying to run with the -vv flag

```
sh-5.1# cat /var/log/rclone.log
2025/08/19 14:01:14 DEBUG : rclone: Version "v1.70.3-DEV" starting with parameters ["rclone" "mount" "ibmcos:bha-coreos" "/root/tmp/bha" "--allow-other=true" "--config=/var/lib/coscsi-config/3d80b31facb6cd6e3f0b4d94b161e706a88be32c7aa5d70faf66f398456c998c/rclone.conf" "--daemon=true" "--log-file=/var/log/rclone.log" "--vfs-cache-mode=writes" "--log-level" "DEBUG"]
2025/08/19 14:01:14 DEBUG : Creating backend with remote "ibmcos:bha-coreos"
2025/08/19 14:01:14 DEBUG : Using config file from "/var/lib/coscsi-config/3d80b31facb6cd6e3f0b4d94b161e706a88be32c7aa5d70faf66f398456c998c/rclone.conf"
2025/08/19 14:01:14 DEBUG : rclone: Version "v1.70.3-DEV" starting with parameters ["/var/usrlocal/bin/rclone" "mount" "ibmcos:bha-coreos" "/root/tmp/bha" "--allow-other=true" "--config=/var/lib/coscsi-config/3d80b31facb6cd6e3f0b4d94b161e706a88be32c7aa5d70faf66f398456c998c/rclone.conf" "--daemon=true" "--log-file=/var/log/rclone.log" "--vfs-cache-mode=writes" "--log-level" "DEBUG"]
2025/08/19 14:01:14 DEBUG : Creating backend with remote "ibmcos:bha-coreos"
2025/08/19 14:01:14 DEBUG : Using config file from "/var/lib/coscsi-config/3d80b31facb6cd6e3f0b4d94b161e706a88be32c7aa5d70faf66f398456c998c/rclone.conf"
2025/08/19 14:01:14 INFO  : S3 bucket bha-coreos: poll-interval is not supported by this remote
2025/08/19 14:01:14 DEBUG : S3 bucket bha-coreos: vfs cache: root is "/root/.cache/rclone"
2025/08/19 14:01:14 DEBUG : S3 bucket bha-coreos: vfs cache: data root is "/root/.cache/rclone/vfs/ibmcos/bha-coreos"
2025/08/19 14:01:14 DEBUG : S3 bucket bha-coreos: vfs cache: metadata root is "/root/.cache/rclone/vfsMeta/ibmcos/bha-coreos"
2025/08/19 14:01:14 DEBUG : Creating backend with remote ":local,encoding='Slash,Dot',links=false:/root/.cache/rclone/vfs/ibmcos/bha-coreos"
2025/08/19 14:01:14 DEBUG : :local: detected overridden config - adding "{8un-i}" suffix to name
2025/08/19 14:01:14 DEBUG : fs cache: renaming cache item ":local,encoding='Slash,Dot',links=false:/root/.cache/rclone/vfs/ibmcos/bha-coreos" to be canonical ":local{8un-i}:/root/.cache/rclone/vfs/ibmcos/bha-coreos"
2025/08/19 14:01:14 DEBUG : Creating backend with remote ":local,encoding='Slash,Dot',links=false:/root/.cache/rclone/vfsMeta/ibmcos/bha-coreos"
2025/08/19 14:01:14 DEBUG : :local: detected overridden config - adding "{8un-i}" suffix to name
2025/08/19 14:01:14 DEBUG : fs cache: renaming cache item ":local,encoding='Slash,Dot',links=false:/root/.cache/rclone/vfsMeta/ibmcos/bha-coreos" to be canonical ":local{8un-i}:/root/.cache/rclone/vfsMeta/ibmcos/bha-coreos"
2025/08/19 14:01:14 INFO  : S3 bucket bha-coreos: vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
2025/08/19 14:01:14 DEBUG : S3 bucket bha-coreos: Mounting on "/root/tmp/bha"
2025/08/19 14:01:14 DEBUG : Root: 
2025/08/19 14:01:14 DEBUG : >Root: node=/, err=<nil>
2025/08/19 14:02:14 DEBUG : rclone: Version "v1.70.3-DEV" finishing with parameters ["/var/usrlocal/bin/rclone" "mount" "ibmcos:bha-coreos" "/root/tmp/bha" "--allow-other=true" "--config=/var/lib/coscsi-config/3d80b31facb6cd6e3f0b4d94b161e706a88be32c7aa5d70faf66f398456c998c/rclone.conf" "--daemon=true" "--log-file=/var/log/rclone.log" "--vfs-cache-mode=writes" "--log-level" "DEBUG"]
2025/08/19 14:02:14 INFO  : S3 bucket bha-coreos: vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
```


```
sh-5.1# ps -ef | grep /root/tmp/bha
root      74795  72993  0 14:01 ?        00:00:00 /var/usrlocal/bin/rclone mount ibmcos:bha-coreos /root/tmp/bha --allow-other=true --config=/var/lib/coscsi-config/3d80b31facb6cd6e3f0b4d94b161e706a88be32c7aa5d70faf66f398456c998c/rclone.conf --daemon=true --log-file=/var/log/rclone.log --vfs-cache-mode=writes --log-level DEBUG
root      75154  73024  0 14:02 ?        00:00:00 grep /root/tmp/bha
```
2

Is this the expected behavior with rclone mount or did I miss any mount option that would allow to mount in lesser time?

3

Can you simplify your config first?

Some parameters like memory_pool_flush_time are no longer used and some like low_level_retries do not belong in config and are simply ignored.

As for 1min mount time the answer is no - rclone does not have any specific timer:). I suggest you run your mount command with -vv flag (debug) and then you should see maybe what is taking so long. As 1 min is exceptionally long time IMO.

EDIT. Actually I see you already posted log file:) But indeed nothing special there.

Could you see how long it takes to run simple:

time rclone lsd ibmcos:bha-coreos:

4

welcome to the forum,

just a guess, maybe test without --daemon

5

@kapitainsky I simplified my config file as below

sh-5.1# cat /var/lib/coscsi-config/3d80b31facb6cd6e3f0b4d94b161e706a88be32c7aa5d70faf66f398456c998c/rclone.conf
[ibmcos]
type = s3
endpoint = ``https://s3.direct.us-south.cloud-object-storage.appdomain.cloud
provider = IBMCOS
env_auth = true
access_key_id = 71fe355282c840d1b9a4537244a9b99c
secret_access_key = deea6abb98f822089afeaa52604a3713fa43828db34c4a58
location_constraint = us-south-standard
bucket_acl=private
max_upload_parts=64
memory_pool_flush_time=30s
acl=private
upload_cutoff=256Mi
chunk_size=64Mi
disable_checksum=true
low_level_retries=3

And then triggered rclone mount with -vv, still I see it takes exactly 1 minute.

sh-5.1# rclone mount ibmcos:bha-coreos /root/tmp/bha2 --allow-other=true --config=/var/lib/coscsi-config/3d80b31facb6cd6e3f0b4d94b161e706a88be32c7aa5d70faf66f398456c998c/rclone.conf --daemo=true --vfs-cache-mode=writes -vv
2025/08/19 14:33:30 DEBUG : rclone: Version "v1.70.3-DEV" starting with parameters ["rclone" "mount" "ibmcos:bha-coreos" "/root/tmp/bha2" "--allow-other=true" "--config=/var/lib/coscsi-config/3d80b31facb6cd6e3f0b4d94b161e706a88be32c7aa5d70faf66f398456c998c/rclone.conf" "--daemon=true" "--vfs-cache-mode=writes" "-vv"]
2025/08/19 14:33:30 DEBUG : Creating backend with remote "ibmcos:bha-coreos"
2025/08/19 14:33:30 DEBUG : Using config file from "/var/lib/coscsi-config/3d80b31facb6cd6e3f0b4d94b161e706a88be32c7aa5d70faf66f398456c998c/rclone.conf"
2025/08/19 14:34:30 DEBUG : rclone: Version "v1.70.3-DEV" finishing with parameters ["/var/usrlocal/bin/rclone" "mount" "ibmcos:bha-coreos" "/root/tmp/bha2" "--allow-other=true" "--config=/var/lib/coscsi-config/3d80b31facb6cd6e3f0b4d94b161e706a88be32c7aa5d70faf66f398456c998c/rclone.conf" "--daemon=true" "--vfs-cache-mode=writes" "-vv"]

6

Myself I have never seen such slow mounting operation and it is a bit suspicious that it is exactly 1min… Like on the clock.

I would try to remove at least memory_pool_flush_time=30s… it should not be used any more according to docs but maybe? And it’s very rounded number which fits perfectly into this 1min delay.

7 
sh-5.1# time rclone lsd ibmcos:bha-coreos --config /var/lib/coscsi-config/3d80b31facb6cd6e3f0b4d94b161e706a88be32c7aa5d70faf66f398456c998c/rclone.conf

real	0m0.533suser	0m0.080ssys	0m0.031s

Calls to cos bucket are actually fast.
And yes I did try by removing memory_pool_flush_time=30s from the config. Still it took whole 1 minute.
Yes since it is exactly 60 secs for every mount, I thought it is some rclone inbuilt setting.
Anything else to debug here?

8

Try the actual rclone binary and not the redhat compiled one.

9

@Animosity022 I am cloning the rclone code from git repo and building the binary as part of my dockerfile. Then copying the rclone binary on to host when the image gets deployed onto kubernetes cluster.

RUN git clone https://github.com/rclone/rclone.git` && cd rclone && git checkout tags/v1.70.3 && go build && ./rclone version && cp rclone /usr/local/bin/rclone`

10

@asdffdsa even without --daemon it still takes 1 minute. But since my actual use case is to mount rclone via csi driver, I would have to run the mount as a background process.

11

Right - Can you just try the mount with the latest binary though without any of that? I’m sure it won’t matter, but it’s a great box to check.

12

This is ringing a bell. I'm pretty sure it is to do with –daemon as you can see the master process exiting after 1 minute in the log.

@Bhagya_shree can you double check you tried it without –daemon ?

There are other ways to to this without –daemon, in bash for example.