Database storage on (SMB-)network volumes with German Umlauts


due to space limitations on my Mac and quite big databases, I need to store my database(s) on a NAS. Yes, I know that this is officially not recommended… :wink:

However, the storage itself on a SMB volume works like a charm, but I have one big problem: German Umlauts.

Mac OS saves all files as UTF-8 decomposed, the Samba server delivers UTF-8 composed. This leads to the problem that documents with Umlauts in their names cannot be accessed anymore.

So how can I solve this issue? Would you alternatively suggest the usage of another protocol? AFP is IMHO not the best option as it isn’t developed furthermore, NFS is originally without user auth (yes, kerberos is available, but causes problems on some Mac OS versions…)



The issue is not the protocol but the underlying filesystem. Afaik, newer. Samba implementations should convert the filenames on the fly.
Which NAS do you use?
Also, an external fish might be a better choice than a NAS.

Fish? :wink:

The only question is if trout or salmon… :wink:

1 Like

Aren’t external fish what you use to store data, one of these dried cods?
Did I mention that I do not really like the autocorrection on iOS (and this is version 17, supposedly with AI – so there must be something to use fish for external storage).

Anyway, back to the original question from @olli: Here’s what I have on a Synology in File services/SMB/Additional settings/macOS:

That works without a flaw here.

I am using a Synology Nas, SMB 3 protocol. Maybe another problem between chair and keyboard on my side regarding the configuration?

External hard drive is nice, but as I have all my paperwork within DT, I replicate the data from my NAS to other locations daily. The NAS is there, anyway and (principially) has the capability to hold the data…why spend more for something which is already there?

IIRC, that option is enabled by default on DSM 7 and higher, but I’ll have a look later on when back at home.

Thanks! :slight_smile:

See my other post. As to the external SSD vs. NAS: Your choice, your decision. I have to access my NAS via WLAN, which is not the best idea for SMB (or any network file system). Therefore I don’t use it to store DT databases.


The NAS is there, anyway and (principially) has the capability to hold the data…why spend more for something which is already there?

People are often using WiFi so performance and reliability is a concern. Hardwiring on gigabit Ethernet is recommended. Also, networked volumes are well known for disconnecting spontaneously. Ethernet is more robust and reliable but that can’t alleviate all the potential for disconnection.

Happy new year, everyone!

I just realized that I never posted my solution to that topic.

Due to copy activities, I managed to mess up my database containing a mixtures of UTF-8 composed as well as UTF-8 decomposed filenames, causing DevonThink not to display those documents with German Umlauts.

The solution I took was to get a neat tool “convmv” (Index of /linux/convmv) and renaming all files inside the database to the (correct) composed version:

(path_to_convmv)/convmv -f utf-8 -t utf-8 --nfc -r --notest ./

Execute this when within the database directory, maybe you try it first without the “–notest” option to see what would happen…

Again: you only need this, if the filenames are already messed up like in my case…I just wanted to post it here for info…

Happy New Year to you and yours as well!

Have you done a File > Verify & Repair Database after you ran your shell commands? If not, you should.

Ok, thanks for the advice!