** Changed in: rsync
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/501532
Title:
rsync rename operation not permitted with SSHFS
--
ubuntu-bugs mailing list
ubuntu
** Changed in: rsync
Status: Unknown => Invalid
--
rsync rename operation not permitted with SSHFS
https://bugs.launchpad.net/bugs/501532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
** Changed in: rsync (Ubuntu)
Status: New => Invalid
--
rsync rename operation not permitted with SSHFS
https://bugs.launchpad.net/bugs/501532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
** Bug watch added: Samba Bugzilla #6077
https://bugzilla.samba.org/show_bug.cgi?id=6077
** Also affects: rsync via
https://bugzilla.samba.org/show_bug.cgi?id=6077
Importance: Unknown
Status: Unknown
--
rsync rename operation not permitted with SSHFS
https://bugs.launchpad.net/bu
I'm going to close this out for this binary package.
There appears to be a work-around for SSHFS where you can add an option
called -oworkaround=rename that will work. I don't know all the
downsides of this --- it states some information regarding the operation
will no longer be atomic as required
Using the command in the test example from the prior comment like:
rsync -a --inplace $HOME/rtest/ $HOME/Net/rtest
Seems to work around the rename issue by writing the remote file in
place. It does have the undesirable property of leaving the remote file
in an unknown state if something happe
Some additional information:
I set up a simple test with more verbose output from rsync below. It
seems that the rename fails but a copy would work. Don't know if that
means it is something with SSHFS now or not. Is there a way to 'force'
RSYNC to always copy a file?
rsync -a $HOME/rtest/ $HO
