Short description of the issue is as follows:
Clients: OSX 10.11.3
We had a long history of non stop problems and issues with
stornext and our osx clients accessing it via SMB, it was so bad we had
to buy a server to re-export the stornext shares so OSX Clients could use the
storage.
When 10.11 came out Quantum said we should use it,
and we were more than happy to.
Things instantly got better. Seen wire speed transfers for
the first time from multiple clients.
But those days were short lived.
We use watch folders on the stornext exported
volumes. Mac users drop files into these watch
folders. We have another service (running on another windows
machine) which watches the watch folders. When it sees new files it grabs
them and performs some work on them (usually transcoding), sends them to a destination then removes the files from the watch folder. This worked for years when we were accessing the volumes via
SMB. But it was always disconnecting and slow.
Now with the LANclient, we havent been able to process
any files in the watch folder since last week.
The problem as I understand it is the transcoding services are
getting stuck on the dot files, or as apple calls them apple
doubles.. These are files that are prefixed with
._ Any file copied to the stornext filesystems will
create a second file prefixed with ._ and near zero kb in size.
With SAMBA you can configure it to veto files, meaning
silently refuse to write files matching this string. So we could
make a regex veto similar to: veto: ^._* and that would
prevent any file prefixed with ._filename from being created on the file
system. I'm told OSX just wasn't making these files before the 10.11/LAN client upgrade (saying this as it wasn't a samba server but a windows 2012R2 one re-exporting the volumes.)
I am hoping to be able to implement something like this to
achieve the same result on our stornext, either at the system, volume or
directory level. Alternatively, if there is a method to do
the same but on the client side, that is just as workable a solution.
Pre 10.11 you could prevent this from happening with a few alterations to com.apple.desktopservices and similar... or use a few of the opensource tools. Now with Apple's introduction of SIP you can not, without turning SIP off, which I would like to avoid as it is not tested, and lord knowswhat elseit will break. I don't want to trade problems. Also these are Avid workstations so I'm sure Avid would have something to say..
any insight or ideas would be fantastic! I opened a ticket with Quantum, I'll see what they have to say but historically they have brought little to the table with our mac related issues. bunch of mac haters. lol
thanks much,
greg