I have tried the workaround option and removed some of the earlier
options:

sshfs [EMAIL PROTECTED]:/afs /afs -oworkaround=rename

And I still get the same error.

>From some of the text on that sshfs FAQ, it sounds as if the rename
problem has been fixed since v1.3.  So I tried another test that
mounts the local disk of a remote system.  It turns out that as long
as AFS isn't in the equation, svn works well with sshfs even *without*
the workaround=rename option.

This leads me to believe it's more of a problem with accessing AFS
than the way renames work through sftp.

On Dec 4, 2:07 pm, Amit Singh <[EMAIL PROTECTED]> wrote:
> On Dec 4, 10:52 am, "[EMAIL PROTECTED]" <lsloan-
>
> [EMAIL PROTECTED]> wrote:
> > Thank you for the very *friendly* reply!
>
> Sure.
>
> A Google search for +svn +sshfs +rename yields (http://
> fuse.sourceforge.net/wiki/index.php/SshfsFaq):
>
> ====
> Why does SVN (etc...) fail to rename files?
>
> $ svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs
> svn: Can't move 'kdelibs/.svn/tmp/entries' to 'kdelibs/.svn/entries':
> Operation not permitted
> The reason is that SFTP protocol version 3 (which is implemented by
> OpenSSH's sftp-server) defines the rename operation slightly
> differently than POSIX. The difference is that renaming to an existing
> file or directory will fail instead of atomically replacing the old
> file.
>
> The -o workaround=rename option will try to emulate POSIX rename
> semantics, but it cannot guarantee atomicity. In most of the cases
> this doesn't matter, and things will work fine with this option.
> ====
>
> What's the output of "sshfs -V" on your system?
>
> Amit
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"macfuse-devel" group.
To post to this group, send email to macfuse-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/macfuse-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to