Simultaneous writes with rclone mount

[Krypto]

Hi,
Is it possible to write multiple files at the same time through the mount? as I have been using the mount and it has only been copying one at a time which has made the uploads really slow.

[Animosity022]

You can copy as many files as you want to the mount. Why do you think it’s only writing one a time? What’s your mount settings? What version are you running?

Example log of 2 files writing at the same time:

2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: Write: len=131072, offset=710672384
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: >Write: written=131072, err=<nil>
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: Write: len=131072, offset=710803456
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: >Write: written=131072, err=<nil>
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: Write: len=131072, offset=710934528
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: >Write: written=131072, err=<nil>
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: Write: len=131072, offset=711065600
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: >Write: written=131072, err=<nil>
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: Write: len=131072, offset=711196672
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: >Write: written=131072, err=<nil>
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: Write: len=131072, offset=711327744
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: >Write: written=131072, err=<nil>
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: Write: len=131072, offset=711458816
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: >Write: written=131072, err=<nil>
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: Write: len=131072, offset=711589888
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: >Write: written=131072, err=<nil>
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: Write: len=131072, offset=711720960
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: >Write: written=131072, err=<nil>
2019/04/20 21:26:12 DEBUG : &{testme2 (w)}: Write: len=131072, offset=711852032
2019/04/20 21:26:12 DEBUG : &{testme1 (w)}: >Write: written=131072, err=<nil>
2019/04/20 21:26:12 DEBUG : &{testme1 (w)}: Write: len=131072, offset=846200832
2019/04/20 21:26:12 DEBUG : &{testme1 (w)}: >Write: written=131072, err=<nil>
2019/04/20 21:26:12 DEBUG : &{testme1 (w)}: Write: len=131072, offset=846331904
2019/04/20 21:26:12 DEBUG : &{testme1 (w)}: >Write: written=131072, err=<nil>
2019/04/20 21:26:12 DEBUG : &{testme1 (w)}: Write: len=131072, offset=846462976

[Krypto]

Hmmm… It might be due to my copying being performed through samba to the mount. I am running v1.47.0-DEV and my mount settings.

/usr/bin/rclone cmount gdrivecrypt: /gdrive --allow-other --attr-timeout 0s --drive-chunk-size 16M --allow-non-empty --dir-cache-time 1m --buffer-size 300M --log-level INFO --transfers 50 --checkers 50 --cache-workers 6 --dir-perms 0777 --file-perms 0777 --vfs-read-chunk-size 16M --max-read-ahead 1000M --fast-list --links --low-level-retries 10 --use-cookies --use-mmap --vfs-cache-max-size 5G --stats 1s --vfs-cache-mode writes --vfs-cache-poll-interval 0.1s --vfs-cache-max-age 5m --write-back-cache

[Animosity022]

Is there a particular reason you are using the beta build? A specific fix?

allow-non-empty is just bad as it allows over mounting and shouldn’t be used.

transfers does nothing on a mount
checkers does nothing on a mount
fast-list does nothing on a mount
max-read-ahead does nothing unless you have happen to running a custom compiled kernel with the parameter set in the kernel.

dir-cache-time 1m - what backend are you using? Is there a reason it’s set low?
-vfs-cache-poll-interval 0.1s - not sure why you’d set this low either.

In your case, you are using vfs-cache-mode writes, which writes everything to local disk first anyway and each time a write is complete, it uploads it.