From d193b19a8f60e8830f0aa5696d2bf3d4fd8d7930 Mon Sep 17 00:00:00 2001 From: Nikolaus Rath Date: Wed, 20 Sep 2017 17:47:52 +0100 Subject: Dropped support for writeback caching As of kernel 4.14, the FUSE module's + writeback implementation is not compatible with network filesystems, and there are no imminent plans to change that. For more details, see https://marc.info/?l=fuse-devel&m=150592103107662&w=2 or As a consequence, the -o unreliable_append option has become obsolete as well. Fixes: #93 Fixes: #88 Fixes: #81 --- sshfs.rst | 15 --------------- 1 file changed, 15 deletions(-) (limited to 'sshfs.rst') diff --git a/sshfs.rst b/sshfs.rst index 7c763dd..dac3108 100644 --- a/sshfs.rst +++ b/sshfs.rst @@ -175,21 +175,6 @@ Options -o password_stdin read password from stdin (only for pam_mount!) --o writeback_cache=BOOL - Enables (*yes*) or disables (*no*) the FUSE writeback cache. When - writeback caching is enabled, write operations are not immediately - sent to the SSH server but first collected and merged locally. This - can significantly improve performance. However, if the file is - changed on the server while there are unsent changes on the client, - data corruption is likely to result. - --o unreliable_append - When writeback caching is enabled, SSHFS cannot reliably support - the ``O_APPEND`` open flag and thus signals an error on open. To - enable support for unreliable ``O_APPEND`` (which may overwrite - data if the file changes on the server at a bad time), mount the - file system with ``-o unreliable_append``. - -o dir_cache=BOOL Enables (*yes*) or disables (*no*) the SSHFS directory cache. The directory cache holds the names of directory entries. Enabling it -- cgit v1.2.3