Crypt mount parameters, are they needed?

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?

Do you have to parameterise a crypt mount as it is a wrapper for an existing mount?

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

rclone v1.74.4

  • os/version: linuxmint 22.3 (64 bit)
  • os/kernel: 7.0.0-14-generic (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.26.5
  • go/linking: static
  • go/tags: none

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

Nextcloud style webdav.

```rclone mount goodcloud: ~/mnt/rclone/goodcloud \
 --vfs-cache-mode writes --vfs-refresh --dir-cache-time 1m0s \
 --use-server-modtime --no-checksum --daemon --allow-non-empty \
rclone mount goodcloud-crypt:/crypt ~/mnt/rclone/goodcloud-crypt \
 --vfs-cache-mode writes --vfs-refresh --dir-cache-time 1m0s \
 --use-server-modtime --no-checksum --daemon --allow-non-empty \```

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

```[goodcloud]
type = webdav
url = https://usexx.thegood.cloud/remote.php/dav/files/user@domain.com
vendor = nextcloud
user = XXX
pass = XXX
nextcloud_chunk_size = 64Mi

[goodcloud-crypt]
type = crypt
remote = goodcloud
password = XXX
password2 = XXX```

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

```No problem it works``

My question is that I have paramterised the mounts for the config "googcloud" and part of the cloud volume called "goodcloud-crypt" which has its own remote path /crypt. Because the crypt mount is a wrapper to I have to restate the VFS cache mode etc or does that carry over from the "goodcloud" mounted remote which it wraps? As it is it works fine but is it more complex than it needs be. It runs as part of a login amnd mount shell script which confirms a remote ping and mount point existence before running.

2

hi, not sure what you are asking?

that points to a subfolder of the current working directory of your local machine.

perhaps that should be
remote = goodcloud:
or
remote = goodcloud:/crypt

3

@asdffdsa I thought you might say that :wink:.#

Would mounting as:

``rclone mount goodcloud: ~/mnt/rclone/goodcloud \
 --vfs-cache-mode writes --vfs-refresh --dir-cache-time 1m0s \
 --use-server-modtime --no-checksum --daemon --allow-non-empty \
rclone mount goodcloud-crypt:/crypt ~/mnt/rclone/goodcloud-crypt \```

Work just as well for the crypt mount. Do I need to restate:

--vfs-cache-mode writes --vfs-refresh --dir-cache-time 1m0s \
 --use-server-modtime --no-checksum --daemon --allow-non-empty \
```

again for the cloud mount?

4

yes
as each mount command needs its own cache and flags.
cannot share the file cache between two mounts.

5

You should not run two copies of rclone using the same VFS cache with the same or overlapping remotes if using --vfs-cache-mode > off