Mac Bug Connecting to Non-Apple SMB Shares

Mac Bug Connecting to Non-Apple SMB Shares

Set my folders free!


Earlier this year we received a number of reports from users that were unable to delete, move or rename documents on a new SMB file share. Eventually we were able to narrow it down enough to be able to consistently duplicate what they were seeing. It appears the SMB client in Mac OS X (10.11, 10.12 and possibly others) is overly aggressive with file locks.

Here is a movie of the bug in action. Many of the Mac administrators we reached out to for confirmation claimed they didn’t see it, until they followed our steps.

The bug seems specific to non-Apple SMB shares (we see it with Microsoft Server 2012r2), we can’t replicate it with OS X Server SMB shares.

Turning on/off Finder previews has no effect. Our machines are not bound to Active Directory. We have confirmed with other institutions that have their clients and server bound to Active Directory and they see the same issue.

We’ve notified Apple and Microsoft about the issue. We have been informed this is an Apple issue, but we have no timeline to share for a fix. We hope Mac OS 10.13 High Sierra will include it.

4 Comments
  • Graham
    Posted at 07:03h, 30 June Reply

    I couldn’t reproduce this on a Synology share, so perhaps it is Microsoft Window Share specific.

    • Richard Glaser
      Posted at 17:24h, 30 June Reply

      Hello Graham:

      Thanks for the feedback

      What version of macOS did you test?

      Can you share your SMB configuration on your Synology share?

      Synology NAS’s appears they could support multiple SMB versions and configurations. We didn’t test against Synology, but a Microsoft Server 2012r2 and Qumulo which is a scale-out NAS http://qumulo.com/.

      But, if you post details of your Synology model and SMB configuration I can add it onto the AppleCare Enterprise problem ticket.

  • Steve Wood
    Posted at 18:19h, 05 July Reply

    We have seen the same behavior on Nasuni (https://www.nasuni.com) caching servers. What we have found is that working in list view mode instead of column view mode seems to alleviate the problem. Not the ideal solution, but it does work. I know that our sys admins have opened this with Apple (I do not have radar info), and I believe Nasuni has also opened a bug with Apple.

    • Richard Glaser
      Posted at 15:47h, 06 July Reply

      Hello Steve:

      Thanks for the feedback. We are doing some testing and will reply back with more details, but according to discussion with Apple “there were a number of factors that worked around the behavior that could contribute to being unable to reproduce the issue”. And it is rumored that macOS High Sierra might fix the issue 😉

      We will post more details, after we have done some more in-depth testing.

Leave a Reply