From 2896f51a22a7531e8dcd362fefe0a4362f3b7422 Mon Sep 17 00:00:00 2001 From: Marcin Zelent Date: Mon, 23 Nov 2020 17:30:58 +0100 Subject: [PATCH] docs: Fixed links to VFS FIle Caching section --- docs/content/commands/rclone_mount.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/commands/rclone_mount.md b/docs/content/commands/rclone_mount.md index b6589117d..3410aec87 100644 --- a/docs/content/commands/rclone_mount.md +++ b/docs/content/commands/rclone_mount.md @@ -112,7 +112,7 @@ 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. +Caching](#vfs-file-caching) section for more info. The bucket based remotes (eg Swift, S3, Google Compute Storage, B2, Hubic) do not support the concept of empty directories, so empty @@ -127,7 +127,7 @@ File systems expect things to be 100% reliable, whereas cloud storage systems are a long way from 100% reliable. The rclone sync/copy commands cope with this with lots of retries. However rclone mount can't use retries in the same way without making local copies of the -uploads. Look at the [file caching](#file-caching) +uploads. Look at the [file caching](#vfs-file-caching) for solutions to make mount more reliable. ## Attribute caching