Re: [sshfs] Problems moving files

[Miklos S. <mi...@sz...>]

> > > For some reason I get this in a sshfs mounted directory:
> > > 
> > >   winooski:~/x eli> touch x
> > >   winooski:~/x eli> touch y
> > >   winooski:~/x eli> mv x y
> > >   mv: cannot move `x' to `y': Operation not permitted
> > > 
> > > It's not a problem of permissions, since I can do this just fine:
> > > 
> > >   winooski:~/x eli> rm y
> > >   winooski:~/x eli> mv x y
> > > 
> > > Is there an option that I'm overlooking, or perhaps this is a bug?
> > 
> > -oworkaround=rename
> > 
> > Needs sshfs-1.3
> 
> Thanks -- that works.  A related question -- is there some kind of a
> FAQ, or a document that describes how to use sshfs more than `--help'?

If you'd like to improve the situation, you _can_ contribute.  For
example by starting a FAQ at:

  http://fuse.sourceforge.net/wiki/index.php/SshfsFaq

> Seems like there are lots of options that could help some
> clarification...  For example -- I noticed some caching issues
> (changes on the server side are visible after a few seconds), and I'm
> sure that some of the `cache' options can be used to change that

Yes, setting 'cache_timeout=1' changes the cache validity timeout to 1
second.  'cache=no' completely disables the cache, so you'd see server
side changes immediately.

> (perhaps `cache_X_timeout' is for that?).

'cache_X_timeout' actually wants to mean either 'cache_stat_timeout',
'cache_dir_timout' or 'cache_link_timeout'.  It's a stupid attempt to
save lines from the usage output :)

> The thing is that I don't know what the tradeoffs are, so I don't
> want to just change things blindly.  The same goes for things like
> `no_readahead' and `sshfs_sync'...

These disable read and write optimizations respectively.  They don't
really make sense unless you are doing something special.

Miklos