Having a bit of trouble following your description of the situation. It'd be helpful if you used actual path names instead of "The one in my user folder" type descriptions.
You have a backup right? Ok then...
The sidebar link is just a shortcut, so it doesn't really mean anything by itself. Fix that last. Just delete it and then re-add it.
Run a disk check and permission repair if you haven't already.
If ~/Desktop
doesn't exist and you're sure it was some how renamed .tsclient, use terminal to move/rename it back. I think its more likely that your ftp client uses that as a temp location and that the files there are only partially downloaded though.
If ~/Desktop
does exist then just move the folder contents back where they belong not the folder itself. Then delete and re-add to the sidebar
In your configuration, you have unix extensions = no
which is fine, but that is why symbolic links on the server are showing up as folders and not aliases. In this mode the server resolves the symbolic links and the client never sees them. If the client tries to create a symbolic link, the server actually generates an alias file, not a host-OS symbolic link. Reasons for this include security (preventing someone from getting access to /etc/passwd
on the server by creating a symbolic link to it) and client compatibility, as OS X and Windows and Unix have slightly different ideas about what constitutes a symbolic link but they pretty much agree on what is a directory or a file.
Permissions issues with SAMBA are complex, so it's not clear that you do not have a permissions issue. Likewise symbolic like resolving is complex, so it is not clear that what you are doing should, in theory work, and there's always the possibility of a bug (most likely in the SAMBA server).
When accessing a SAMBA server from a Mac, these identities and permissions are involved:
- The Mac User you are logged into the Mac as
- The SAMBA user you are logged into the SAMBA server as
- The SMABA server host OS user you get converted to
- Unix-style file permissions
- For NTFS and HFS+, associated file-system ACLs
So even though you have provided a lot of information, it's still not clear that you are not having permissions problems. The fact that you can mv
and cp
on the server (using what account?) does not mean you do not have a permissions problem preventing you from doing it on the client (using what accounts and with what effective account on the server?).
If the server is supporting ACLs and since you have options like inherit permissions = yes
and inherit acls = yes
set there could be some kind of ACL problem that is only allowing read access to directories accessed via symbolic links. There are several other avenues of investigation based on the server configuration.
I would really expect you should be able to find more information in the SAMBA server logs than you have communicated. They should give you a much better sense of exactly what is being denied.
For what it is worth, I tried to duplicate your setup using an Ubuntu 12.04 host as the SAMBA server and could not reproduce your problem. Symbolic links worked for me as expected.
Best Answer
Open your terminal (Terminal.app)
Then do:
mv source_folder destination_folder
e.g:
mv /Users/foo/Music/ /Users/foo/something
This is way faster than copying as it maintains
inode