Samba and git

After upgrading the operating system to OS Ventura, our infrastructure (based on an integration between samba and git) does not work anymore.

On our machines we mount several volumes via the SMB3 protocol and, on these volumes, there are folders that are versioned through git.

Before OS Ventura the whole infrastructure works correctly, then (after some interaction with the contents of the folders) using git returns the error "Bus Error 10" and git stops working. To correct the problem you have to unmount the volume and remount.

We tried updating git and compiling it directly on the machine with OS Ventura, but that's don't solve the problem.

The console log show the following message:

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_MEMORY_ERROR at 0x00000001033a4000
Exception Codes: 0x000000000000000a, 0x00000001033a4000


Termination Reason: Namespace SIGNAL, Code 10 Bus error: 10
Terminating Process: exc handler [6774]


VM Region Info: 0x1033a4000 is in 0x1033a4000-0x1033a8000; bytes after start: 0 bytes before end: 16383
      REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
      mapped file 1033a0000-1033a4000 [ 16K] r--/rwx SM=COW ...t_id=e20a2081
---> mapped file 1033a4000-1033a8000 [ 16K] r--/rwx SM=COW ...t_id=e1274f81
      GAP OF 0x38000 BYTES
      Kernel Alloc Once 1033e0000-1033e8000 [ 32K] rw-/rwx SM=PRV

Mac mini, macOS 12.0

Posted on Dec 22, 2022 12:59 AM

Top-ranking reply

James Brickley

Level 5

5,608 points

Posted on Dec 22, 2022 07:05 AM

You might well have encountered a bug in Ventura. Are you running the latest 13.1 version? It is not uncommon for a new release of macOS to have initial problems in a corporate or enterprise network. The modus operandi in these environments is to test a new OS prior to deploying to production use. Meaning, if Ventura doesn't work then don't deploy Ventura to the users. Many Mac users in corporate environments find that it's a Windows shop and they are on their own to support themselves. In this case, you've identified a problem in your environment so you should tell the user base not to upgrade to Ventura. There is little reason to upgrade to Ventura as all the latest Apple Developer tools run on Monterey just fine and you don't yet have to upgrade to Ventura to use the latest Xcode, etc. It's not uncommon for corporate networks to have macOS a version behind for 6 months to a year. This is beneficial as Apple typically releases several dot releases for macOS in the first year that fix many bugs. It's one thing to run the cutting edge macOS on a personal home Mac and something entirely different in any business environment.

The macOS implementations of SMB have had their struggles over the years and I find NFS to be more stable. However, setting up NFS properly is what some may consider to be old-school UNIX gray-beard black magic.

While git should work properly using local protocol over SMB or NFS shares, it is not the preferred nor recommended way of using a shared git repository in a corporate LAN environment. Most everyone uses git over httpd behind a web server and that is the preferred way of accessing a git repository. I would suggest setting up a web server and move the storage locally to the server. It will run faster than any network share SMB/NFS solution. You could add on a lightweight web interface such as Gitea or others. It's easier to secure the repos and manage them with a web UX.

Sounds like your needs do not include GitHub / GitLab level features if you are running local repos over an SMB share. But they are options to consider. With a corporate GitHub account you can have a private domain and private repos. GitLab can do the same but you can also run your own on-prem GitLab servers.

View in context

Samba and git

Similar questions