I've just the MediaHarmony Samba VFS module to work with latest Samba.? If you've ever tried to run multiple Avid clients from a single Samba share (and discovered the corruption and crashes that happen) you might be interested.
Original project:
http://ingex.sourceforge.net/MediaHarmony/
I've updated only the media_harmony module so far.? The other parts look interesting, but I don't have a reason to work on them right now.
My employer has agreed to let me release the code as GPL, and Jeremy Allison has said positive (if non-committal) things about including it in a future Samba release.? Mailing-list discussion here:
https://lists.samba.org/archive/samba-technical/2012-March/082359.html
...and official "please add media_harmony to Samba" request here:
https://bugzilla.samba.org/show_bug.cgi?id=8841
If you're interested in testing and reporting bugs (or encouraging the Samba developers to include it), I'd love to have you try it out.? I've also got a version that compiles against the current Samba 3.6.3 release available that I'd be happy to send you via email.? (There are slight differences between Samba 3.6.3 and git-latest Samba that require minor module changes.)
Background info:
Part of the legacy from Avid's days as a dedicated-hardware system is that multiple Avid systems do not play nicely together on shared storage.? They overwrite and corrupt each other's database files and interrupt each other's processing.? Fully shared Avid storage with a vanilla Samba server is effectively impossible because of this.
There are solutions to the problem, but they're sold (by the vendor and others) for $40K-$100K USD and up.? There are also workarounds that involve complex arrangements of permissions settings and file copying, but they impede and confuse the workflow as much as they facilitate it.
The media_harmony VFS module is a simple, elegant solution to the problem from the user's point of view (though it's a bit of a hack from a developer's point of view).? The small handful of troublesome files are kept separate per client on the server, while each Avid client system sees those files exactly where it expects them to be.
Andrew