mv causes strange behavior with symbolic links

[Joseph Bylund]

1) Description: Ubuntu 10.04.1 LTS
Release: 10.04

2) sshfs:
  Installed: 2.2-1build1
  Candidate: 2.2-1build1
  Version table:
 *** 2.2-1build1 0
        500 http://ubuntu.media.mit.edu/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status
     2.2-1 0
        500 http://ubuntu.media.mit.edu/ubuntu/ karmic/main Packages

3) when moving folder to ../newfolder name expected to find it in pwd/../newfoldername
4) actually found folder in ../newfoldername on remote machine mounted by sshfs

In words:
When working in a directory that is a symbolic link to a directory on an sshfs drive/filesystem and moving a folder to ../newfoldername, instead of ending up in ../newfoldername from pwd, it ends up in ../newfoldername on the remote computer that is mounted by sshfs.

An example:
ls -l ~/lib

total 568
drwxr-xr-x 2 user user 4096 2010-04-15 14:07 evrmsd_old/
-rw-r--r-- 1 user user 553004 2010-08-06 14:29 new_message.wav
drwxr-xr-x 5 user user 4096 2010-01-16 17:58 old_structurelib/
lrwxrwxrwx 1 user user 58 2010-02-04 13:22 structurelib -> /home/user/remote_drives/sshfs_home/lib/structurelib/
drwxr-xr-x 4 user user 4096 2010-01-22 16:32 structurelib_1/
drwxr-xr-x 2 user user 4096 2010-08-10 12:52 structurelib_8_10/
drwxr-xr-x 2 user user 4096 2010-08-17 14:20 structurelib_8_17/
drwxr-xr-x 3 user user 4096 2010-04-15 16:08 structurelib_work/

cd structurelib
ls

somedir

mv somedir ../newsomedir

cd ..
ls
newsomedir is not listed. newsomedir ends up in home on the sshfs mounted machine in ~/lib.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: sshfs 2.2-1build1
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Wed Aug 18 11:31:10 2010
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: sshfs-fuse