wanted to mount a linux web server to my Ubuntu workstation so could use subversion.
Using samba, kept getting errors.
So installed fuse and set it up to mount a drive.
got this error:
svn+ssh: xxxsvnm.server.ddu/local/svn/IMFO/hrisDocs/persinfo/appointmentHistory/ appointmentHistory
svn: Can't move 'appointmentHistory/.svn/tmp/entries' to 'appointmentHistory/.svn/entries': Operation not permitted
The fix was using the switch ‘workaround’ because apparently fuse (depending on version) has a problem with renaming certain files.
So now my /etc/fstab entry reads:
sshfs#gare@128.252.33.210: /media/imfodevel fuse user,allow_other,umask=002,workaround=rename 0 0
And am able to mount and use the drive with no problem!
read more about fuse here http://www.ubuntux.org/fuse-sshfs
Submitted by msabramo on Tue, 2006-02-21 22:57.
FUSE (Filesystem in Userspace) rocks. Case in point, sshfs. – It’s a filesystem client based on the SSH File Transfer Protocol. Since most SSH servers already support this protocol it is very easy to set up: i.e. on the server side there’s nothing to do. On the client side mounting the filesystem is as easy as logging into the server with ssh.
more:
====
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?
source: http://www.mail-archive.com/macfuse-devel@googlegroups.com/msg00562.html
I’m using ubuntu 8.04 and
sshfs -V
SSHFS version 1.9
FUSE library version: 2.7.2
fusermount version: 2.7.2
using FUSE kernel interface version 7.8
i’m not usind fstab and the soluction for me whas
sshfs user@192.168.0.1:/path/ path -o workaround=rename
Thx for help
[]‘s Anselmo Battisti
sshfs user@192.168.0.1:/path/ path -o workaround=rename
works for me, thanks a lot
Many thanks – works for me (fixed my svn problem)
Although (even with password free pub/private key), I can’t get it to work (ever) from fstab, but that’s not a problem I’ve got a bash script that runs mounts, not a biggie to do.
Thanks.
Hi James,
Yes I have same situation with current version of FUSE. I have to mount after boot so now in my /etc/fstab I use the noauto option:
# Don’t mount on boot Mar 25
sshfs#lhcu@121.222.56.000: /media/devel fuse noauto,user,allow_other,workaround=rename 0 0
………
My current fuse version: ( On Ubuntu 10.04)
$ sshfs –version
SSHFS version 2.2
FUSE library version: 2.8.1
fusermount version: 2.8.1
using FUSE kernel interface version 7.12