docs: Fixed links to VFS FIle Caching section

This commit is contained in:
Marcin Zelent 2020-11-23 17:30:58 +01:00 committed by GitHub
parent 5b9115d87a
commit 2896f51a22
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -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 sequentially, it can only seek when reading. This means that many
applications won't work with their files on an rclone mount without applications won't work with their files on an rclone mount without
"--vfs-cache-mode writes" or "--vfs-cache-mode full". See the [File "--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, The bucket based remotes (eg Swift, S3, Google Compute Storage, B2,
Hubic) do not support the concept of empty directories, so empty 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 systems are a long way from 100% reliable. The rclone sync/copy
commands cope with this with lots of retries. However rclone mount 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 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. for solutions to make mount more reliable.
## Attribute caching ## Attribute caching