I am using version 1.4.50 for macos
when asking claude to help check if rclone global flags are being passed to the mount and compare this is what I get:
The mount is up but the VFS stats are still showing the old values — ReadAhead: 0, CacheMaxSize: 257GB, CacheMinFreeSpace: -1, NoChecksum: false. The daemon-level options are correct (we verified that), but the mount itself was created by RcloneView’s UI with its own hardcoded parameters that override the daemon defaults at mount time.
This confirms the core problem: RcloneView passes its own VFS parameters when creating the mount via RC API, which override whatever the daemon’s default settings are. The daemon knows about our flags, but RcloneView’s mount creation call explicitly sets its own values on top.
The flags I am trying to pass: –drime-upload-cutoff 1M --transfers 16 --checkers 16 --multi-thread-streams 0 --timeout 5m --contimeout 60s --retries 8 --drime-hard-delete --vfs-read-ahead 3G --vfs-read-chunk-size 256M --vfs-read-chunk-size-limit 2G --buffer-size 128M --vfs-cache-min-free-space 10G --vfs-fast-fingerprint --no-checksum --no-modtime --s3-chunk-size 128M --s3-upload-concurrency 8
versus what is shown for the actual mount once up:
Applications/RcloneView.app/Contents/MacOS/rclone_arm64 rc vfs/stats fs=’drive name’: --rc-user=admin --rc-pass=admin --url http://127.0.0.1:5582 2>&1 | grep -E ‘“ReadAhead”|“CacheMaxSize”|“CacheMaxAge”|“CacheMinFreeSpace”|“NoModTime”|“NoChecksum”|“CacheMode”’ localhost:/drive on /Users/drive (nfs, nodev, nosuid, mounted by bridgett) “CacheMaxAge”: 86400000000000, “CacheMaxSize”: 257698037760, “CacheMinFreeSpace”: -1, “CacheMode”: 3, “NoChecksum”: false, “NoModTime”: false, “ReadAhead”: 0,
Update - injecting global rclone flag for cache dir works but the GUI for advanced options for mount manager is not working; also none of the vfs rclone flags are passing through and are being ignored
