rsync - Jan 2009 - DO NOT REPLY [Bug 6077] New: rsync doesn't modify content of sshfs volumes

https://bugzilla.samba.org/show_bug.cgi?id=6077

           Summary: rsync doesn't modify content of sshfs volumes
           Product: rsync
           Version: 3.0.2
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: core
        AssignedTo: wayned@samba.org
        ReportedBy: diego.guadagnoli@roma1.infn.it
         QAContact: rsync-qa@samba.org


I use rsync daily for backups.
I recently tried rsync to backup some dirs in my local machine into dirs
mounted
as sshfs volumes in a remote machine.
While it correctly transfers files not already existing in the recipient, it
fails to modify the content of existing ones or to delete them if extraneous
(option --del).

What I get is an error like:
rsync: rename <tmp filename in the recipient> -> <real filename in
the
recipient>: Operation not permitted (1)

rsync error: some files could not be transferred (code 23) at main.c(1031)
[sender=3.0.2]

I wonder whether there are sshfs or rsync flags that would fix this.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

https://bugzilla.samba.org/show_bug.cgi?id=6077


matt@mattmccutchen.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Comment #1 from matt@mattmccutchen.net  2009-01-31 00:02 CST -------
This is not an rsync bug.

It looks like passing "-o workaround=rename" to sshfs might make
renames work.
If not, you can pass --inplace to rsync to avoid renames.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.