-
Notifications
You must be signed in to change notification settings - Fork 269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connect to win10: Can read/write, but cannot rename/delete (however, Connect to ubuntu 20.04 using net use
works well)
#244
Comments
Hi. I'm experiencing exactly the same issue. Could somebody please help us resolve this issue? |
When accessing ssh-server of Windows 10, the set permissions are slightly different from those of Linux. In my opinion, the difference in the form of permission notation may cause an error. |
Same issue here. Any workarounds? |
I don't even get an error when deleting files; they just don't delete. I wish i knew how to see some sort of log for this tool. |
I think it may not be the fault of sshfs-win. When I mounted a Win10 OpenSSH session on WSL2 and opened it in Windows Explorer, the behavior was similar.
sudo sshfs -o reconnect,allow_other,follow_symlinks,ServerAliveInterval=15,ServerAliveCountMax=3 [email protected]: /mnt/x
The difference is that in the case of WSL2, error 0x80070032 occurs. |
But it does work perfectly well with WinSCP. |
It also works perfectly with Mountainduck (Cyberduck). So, the fault has to be with SSHFS-Win or WinFsp. |
Just installed winfsp-1.9.21096 and sshfs-win-3.5.20357-x64 and the problem is still present. |
hi, |
Hi, I found solution that works with my synology NAS: |
Same issue experienced here (unable to rename / move / delete existing files), when accessing OpenSSH 8.6/Win32 on Windows 10 and Windows Server 2019. |
Bummer deal. This open issue is a complete show stopper for sure. |
Same issue here with |
Same issue, |
Just installed winfsp-2.0.23075.msi + sshfs-win-3.5.20357-x64.msi + sshfs-win-manager-setup-v1.3.1.exe on Windows 10 Pro, mounting remote SFTP from XigmaNAS (FreeBSD) and the problem is gone. Was this issue fixed in the meantime, or is this working correctly now because of XigmaNAS ... remains to be seen. |
Just installed winfsp-2.0.23075.msi and sshfs-win-3.5.20357-x64.msi. And it is slow indeed |
I guess something is off with the permission mapping when connecting to a Windows-SSH-server. Checking with "fsptool-x64.exe perm", I get these permissions. Renaming and deleting not working (doesn't matter if SSH user is admin or normal user or file has Public:F permission): Permission mapping to a Linux-SSH-server looks less complicated. Renaming and deleting works fine: Is there any way to configure permission mapping on mounting? Mounting with -o umask=0770 seems to get ignored. |
I did some further testing: fsptool perm test.txt: fsptool perm testfolder: tested mount options: create_file_umask=0000,create_dir_umask=0000,umask=0000,idmap=user no options workaround=rename,from_code=UTF8,to_code=ANSI workaround=rename,from_code=UTF8,to_code=UTF-16 allow_other,allow_root,use_ino fsname=ntfs,subtype=ntfs |
I know this is an old thread, but was it ever fixed? |
I'm running sshfs-win trying to connect to a drive located on a Windows Server 2019 instance and I'm running into the issue where when I try to rename a file I get the error "You require permission from S-1-5-21-449734894-1124184469-618129862-500 to make changes to this file". SSHFS as a protocol uses SFTP through SSH, I can able to rename files just file through SSH, as well as SFTP, I believe this has to be a bug with the way SSHFS works. So no, I hope someone does find a fix though kazdans does have an interesting fix higher in this thread for his NAS: Inside my drives recycling $RECYCLING.BIN folder there is a folder called " S-1-5-21-449734894-1124184469-618129862-500", I'm not sure if that's an identifier for the drive itself, but if I can find a way to disable to generate of that file like kazdans did with their NAS, that may solve the problem. |
Hi, Any update with this? I cannot rename the files. I can do other actions except that. |
Thanks for this tool, really helpful!
Working cases
It works fine when I connect to a ubuntu 20.04 machine, using
net use X: \\sshfs.kr\union@my_linux_machine
.can read/write/modify/delete.
Failed cases
However, when I connect to another win10 machine, I cannot rename files/folders, or delete files/folders.
I have 2 win10 machines, and I tried on both sides, not working.
Compare with ubuntu sshfs
Then I try to connect to win10 machine from a ubuntu 18.04 machine using sshfs, works fine, so not win10's problem.
What I have tried
I tried those commands, they have the same problem (can read/write, cannot modify/delete). (my_host is a valid host name):
I also cleared my PATH variable to contain only sshfs-win's bin:
no effect. But if I connect to a linux machine, just
net use X: \\sshfs.kr\union@my_linux_machine
can work well.Problem: Cannot rename
Problem: Cannot delete
When I delete a file, it seems it is deleted, but when I refresh, it comes back.
The text was updated successfully, but these errors were encountered: