On OSX ExFat partition the following worked for me. $SHADER is the shader file that unity reports in the error message.

cat $SHADER
(copy shader contents on the terminal)
rm $SHADER
vim $SHADER
(post shader contents into vi and save)

Creating the file as the user that will run Unity seems to work around the problem. You may have to do this multiple times, opening the project or doing import until each item is discovered.

This still happens in 2018.1.0b10, my exFAT Samsung T5 gets "attempt to write a readonly database" on asset import for my ~600mb project. I had to move everything to my internal APFS drive.

please fix it, i have this iusse too

I have the same Problem.
After importing Textmesh Pro into my project Unity keeps crashing while importing the Shaders.
I tried running as ``sudo`` but this doesn't help.

I'm Using Unity 2017.1.0f3 Personal on macOS Sierra (10.12.5 (16F73)) and the Unity Project I try to open is located on an exFAT formated HDD.
The project directory is (yes I'm German):
```
/Volumes/Daten/Medien/Programmieren/Unity/BW_Naturschutz_Memory/Assets/TextMesh Pro/Resources/Shaders
```

In my case, happened after cloning a Git project repo to an external SSD, exFAT too. Since the Library is ignored, Unity needs to reimport everything, and the crash occurred just when importing a shader.

My Editor log:

[Updating a bunch of shaders before this one]
Updating Assets/Standard Assets/Effects/ImageEffects/Shaders/_Antialiasing/DLAA.shader - GUID: 017ca72b9e8a749058d13ebd527e98fa...
attempt to write a readonly database

(Filename: /Users/builduser/buildslave/unity/build/External/sqlite/SQLite.cpp Line: 345)

The database in question is probably Library/ShaderCache.db