Specifically network shares with lots of files (in my case 30,000). The share is an SMB share on Unraid if that makes any difference. Every time I open it, I get the Beachball of Death and every open Finder window hangs. Is it the sheer number of files causing the problem or is there more to it?
Any issues opening network shares?
- Thread starter Bluecube
- Start date
macOS is comically poor at keeping shares mounted, try https://apps.apple.com/us/app/automounter/id1160435653?mt=12 and see if it helps.
I have no issues with my Synology NAS but then again I don't have 30k files.
I have no issues with my Synology NAS but then again I don't have 30k files.
I don't have any issues mounting the shares (I've got Automounter already but thanks for the pointer) but accessing them can be a bit hit and miss. Especially in the case I've just described. I'm still waiting for the file list to show up at the moment.
What's the backing storage? Isn't UnRAID effectively limited to single disk speed? macOS might be trying to index the files and if it's on an old spinner that could be why you get the beachball.
Last edited:
Soldato
Apple's implementation of samba is truly pants and you're arguably better with NFS (doesn't play nice for TM or various Apple libraries) or AFP (until Apple EOL client AFP).
But splitting up the current share into directories with fewer files, i typically stick to a few thousand, massively helps.
Other options you can try within MacOS is to enable DSDontWriteNetworkStores to stop creation and reading of .DS_Store files (sounds like you've already done this); confirm client-side packet signing is disabled (should be on 13.4+) otherwise disable it; disable Finder's icon previews by pressing CMD + J in your directory, uncheck Show icon preview (click Use as Defaults if you want to make it global).
I've never really delved into Unraid but see if you can enable the samba vfs_fruit module which attempts to improve compatibility with MacOS (it can help but it can also cause other headaches, especially in mix platform environments), otherwise see if you can enable AFP (or Netatalk) or NFS for your shares and give that a whirl.
Edit - Quick Google found these that might be worth a read, Unraid and vfs_fruit and a Netatalk plugin.
But splitting up the current share into directories with fewer files, i typically stick to a few thousand, massively helps.
Other options you can try within MacOS is to enable DSDontWriteNetworkStores to stop creation and reading of .DS_Store files (sounds like you've already done this); confirm client-side packet signing is disabled (should be on 13.4+) otherwise disable it; disable Finder's icon previews by pressing CMD + J in your directory, uncheck Show icon preview (click Use as Defaults if you want to make it global).
I've never really delved into Unraid but see if you can enable the samba vfs_fruit module which attempts to improve compatibility with MacOS (it can help but it can also cause other headaches, especially in mix platform environments), otherwise see if you can enable AFP (or Netatalk) or NFS for your shares and give that a whirl.
Edit - Quick Google found these that might be worth a read, Unraid and vfs_fruit and a Netatalk plugin.
Last edited:
I think it's time to reinstall MacOS on my Studio. The current install came from a five year old iMac and I think there's just too much accumulated crud. I've had the occasional network issue recently and I think something network related is causing the Finder lock up. I've tried accessing the same share on my MBP and while it's still slow to show the files, it's significantly faster, actually shows the files and Finder doesn't lock whilst the file list is being pulled.
@visibleman - thanks for those various pointers to vis_fruit. I wasn't aware of those options despite my own googling.
@visibleman - thanks for those various pointers to vis_fruit. I wasn't aware of those options despite my own googling.