diff options
author | G.raud Meyer <graud@gmx.com> | 2018-03-20 08:18:34 +0100 |
---|---|---|
committer | Nikolaus Rath <Nikolaus@rath.org> | 2018-03-28 19:48:02 +0100 |
commit | 303126bad91a536b4173ec3932aa312823729cbb (patch) | |
tree | 79230746df136a9fc4f921a6946a46b186399ce5 /sshfs.rst | |
parent | f0a0cc2b7e7d837946af7597caf9cc7394f238dc (diff) | |
download | sshfs-303126bad91a536b4173ec3932aa312823729cbb.tar sshfs-303126bad91a536b4173ec3932aa312823729cbb.tar.gz sshfs-303126bad91a536b4173ec3932aa312823729cbb.tar.bz2 sshfs-303126bad91a536b4173ec3932aa312823729cbb.zip |
New workaround renamexdev to enable moving files across remote filesystems
sshfs.rst: update the documentation.
Diffstat (limited to 'sshfs.rst')
-rw-r--r-- | sshfs.rst | 13 |
1 files changed, 13 insertions, 0 deletions
@@ -107,6 +107,8 @@ Options :rename: Emulate overwriting an existing file by deleting and renaming. + :renamexdev: Make rename fail with EXDEV instead of the default EPERM + to allow moving files across remote filesystems. :truncate: Work around servers that don't support truncate by coping the whole file, truncating it locally, and sending it back. @@ -228,6 +230,17 @@ removed it, but before SSHFS had the time to rename the old file. In this case, the rename will still fail. +Permission denied when moving files across remote filesystems +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Most SFTP servers return only a generic "failure" when failing to rename +across filesystem boundaries (EXDEV). sshfs normally converts this generic +failure to a permission denied error (EPERM). If the option ``-o +workaround=renamexdev`` is given, generic failures will be considered EXDEV +errors which will make programs like `mv(1)` attempt to actually move the +file after the failed rename. + + SSHFS hangs ~~~~~~~~~~~ |