Depending on the startingpoint of a Spotlight search in Macos Finder, the search fails. ### Env smbd -V Version 4.18.2 Fruits: fruit:veto_appledouble = yes fruit:aapl = yes fruit:nfs_aces = no fruit:metadata = stream fruit:resource = xattr fruit:copyfile = yes vfs objects = catia fruit streams_xattr recycle shadow_copy2 Samba Spotlight Backend: Elasticsearch Macos Ventura 13.2 Filesystem: Ubuntu included ZFS ### Setup /myshare/MYSUBDIR_Ä/files/doc1.pdf /myshare/MYSUBDIR/files/doc2.pdf ### Success and Fail Doing the following in Macos Finder: enter directory and search if starting my Spotlight search from folder "/myshare", both "doc1.pdf and "doc2.pdf" CAN be found by name. if starting my Spotlight search from folder "/myshare/MYSUBDIR", then "doc2.pdf" CAN be found by name. if starting my Spotlight search from folder "/myshare/MYSUBDIR_Ä", then "doc1.pdf" CANNOT be found by name. ### My guess I suspect that Spotlight sends a directory string that is somehow corrupted when reaching samba. Other characters may suffer from this too.
I suspect combined diaeresis. My folder "MYSUBDIR_Ä" contains that nasty double character. This is however not in the elasticsearch db. It seems samba produces these, as the folder name seen by Linux is a normal single character. Is there a way to disable combined diaeresis in Samba, so the Mac gets a real Umlaut in the first place? Thanks M
Note: Updated to Ventura 13.4. Bug persists.
I ran into this as well but in my case the share name has the umlaut. Fast searches don't work at all and Finder starts a full directory travelsal. Removing the umlaut from the share name instantly fixes the issue, even without reindexing the directory structure. But obviously Samba should support special characters since native macOS SMB & Spotlight do as well. Hopefully we get a fix at some point.