From 3a7bb7b2dfa4b9cb7e899ebc0d8d9aae73d87461 Mon Sep 17 00:00:00 2001 From: Nick Craig-Wood Date: Sat, 10 Feb 2018 09:28:20 +0000 Subject: [PATCH] mount: update docs showing --vfs-cache-mode to work around limitations --- cmd/mountlib/mount.go | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/cmd/mountlib/mount.go b/cmd/mountlib/mount.go index 1c866cdf8..9334e6176 100644 --- a/cmd/mountlib/mount.go +++ b/cmd/mountlib/mount.go @@ -116,9 +116,11 @@ which creates drives accessible for everyone on the system. ### Limitations -This can only write files sequentially, it can only seek when reading. -This means that many applications won't work with their files on an -rclone mount. +Without the use of "--vfs-cache-mode" this can only write files +sequentially, it can only seek when reading. This means that many +applications won't work with their files on an rclone mount without +"--vfs-cache-mode writes" or "--vfs-cache-mode full". See the [File +Caching](#file-caching) section for more info. The bucket based remotes (eg Swift, S3, Google Compute Storage, B2, Hubic) won't work from the root - you will need to specify a bucket,