Closed Jo-Con-El closed 4 years ago
Thanks for the report, and apologies for not responding for so long! I am afraid I have no idea what to do here. I don't use MacOS and have no idea find Finder may be bothered by. So unless someone with Mac skills shows up to work on this, I'm afraid this won't be fixed..
@bfleischer Would you be able to help?
@Nikratio I'm probably having a similar issue as the reporter - I have a file with Japanese characters in the name. The name is displayed properly, but Finder won't make a preview, and won't properly launch associated application. Using the open command also results in "No such file or directory" error.
unique: 3, opcode: ACCESS (34), nodeid: 1, insize: 48, pid: 23366 access / 01 unique: 3, success, outsize: 16 unique: 4, opcode: ACCESS (34), nodeid: 13, insize: 48, pid: 23366 access /_michal 01 unique: 4, success, outsize: 16 unique: 6, opcode: ACCESS (34), nodeid: 169, insize: 48, pid: 23366 access /_michal/NicoVideo 01 unique: 6, success, outsize: 16 unique: 7, opcode: LOOKUP (1), nodeid: 169, insize: 133, pid: 23366 LOOKUP /_michal/NicoVideo/【Kagamine Rin & Len】Electric・Angel えれくとりっく・えんじぇぅ-720p.mp4 getattr /_michal/NicoVideo/【Kagamine Rin & Len】Electric・Angel えれくとりっく・えんじぇぅ-720p.mp4 unique: 7, error: -2 (No such file or directory), outsize: 16 unique: 2, opcode: LOOKUP (1), nodeid: 169, insize: 133, pid: 23366 LOOKUP /_michal/NicoVideo/【Kagamine Rin & Len】Electric・Angel えれくとりっく・えんじぇぅ-720p.mp4 getattr /_michal/NicoVideo/【Kagamine Rin & Len】Electric・Angel えれくとりっく・えんじぇぅ-720p.mp4 unique: 2, error: -2 (No such file or directory), outsize: 16 unique: 5, opcode: STATFS (17), nodeid: 1, insize: 40, pid: 1064 statfs / unique: 5, success, outsize: 96
I suspect this may be due to Mac-specific unicode normalization requirements, see:
EDIT: More useful links regarding normalization on macOS:
What's interesting, is that using cp in Terminal works to copy the file over to local storage, and VLC can play the file as long as it's dragged into the app from Finder - using VLC' Open dialog doesn't work. Is there a way to determine what the actual (hexdump-style) file name is on server (Linux), client? I'm expecting to find a mismatch somewhere here.
You could try to add a few printf
into sshfs.c, probably in the readdir
handler function.
Any updates on this? I am having the same problem
This solution fixes my problem: https://github.com/osxfuse/osxfuse/issues/71#issuecomment-12762017
Seems this was an issue in osxfuse then, rather than SSHFS. Thanks for following up!
There's a weird interaction here with Finder and SSHFS where I cannot access a directory with an accented letter, but I can chdir into it from the command line.
SSHFS version 2.10 OSXFUSE 3.7.1 FUSE library version: 2.9.7 fuse: no mount point
On the command line it seems to work fine:
But when I use Finder and click on the Documentación directory under ~/cowcow/tmp/, I see an empty directory. If I put sshfs in debug mode, I get a No such file or directory error:
I sent the output to a file and inspected it, and what I see is a UTF-8 string.
Thanks!