Hello!
We are running into what seems to be a long-standing error between OSX and SAMBA based SMB/CIFS servers.
When copying files (usually images or media files, but maybe that is because that is what we predominantly use) in OSX Finder, our users are often presented with the error: The operation can’t be completed because the item “[item name]” is in use.
Using google-fu this seems like something people have been fighting with since apple moved away from SAMBA to their own SMB stack.
We've followed all of the suggestions out there (most of which are forcing CIFS(SMB1) which we do at both the server and client level) with no luck.
If we use a program other than finder to copy then the copy works just fine, so what we believe is happening is the finder is trying to open the files r/o after they are created but before data is copied, which causes this error. (in my debugging, the way OSX finder creates a file is to open/close a 0 byte file and then open it with append to write data, so I think the r/o access is happening in that interval between the initial creation and append)
I'm wondering if there is a configuration level solution on the FreeNas/Samba side that could help?
There are some older threads I've found but none of them seem to have reached a resolution. If this has been solved I apologize for wasting time.
Thanks!
Tech Details:
FreeNAS-9.3-STABLE-201602031011 on a SuperMicro based system with 256GB RAM and ~450TB usable space, using AD as auth source.
We are running into what seems to be a long-standing error between OSX and SAMBA based SMB/CIFS servers.
When copying files (usually images or media files, but maybe that is because that is what we predominantly use) in OSX Finder, our users are often presented with the error: The operation can’t be completed because the item “[item name]” is in use.
Using google-fu this seems like something people have been fighting with since apple moved away from SAMBA to their own SMB stack.
We've followed all of the suggestions out there (most of which are forcing CIFS(SMB1) which we do at both the server and client level) with no luck.
If we use a program other than finder to copy then the copy works just fine, so what we believe is happening is the finder is trying to open the files r/o after they are created but before data is copied, which causes this error. (in my debugging, the way OSX finder creates a file is to open/close a 0 byte file and then open it with append to write data, so I think the r/o access is happening in that interval between the initial creation and append)
I'm wondering if there is a configuration level solution on the FreeNas/Samba side that could help?
There are some older threads I've found but none of them seem to have reached a resolution. If this has been solved I apologize for wasting time.
Thanks!
Tech Details:
FreeNAS-9.3-STABLE-201602031011 on a SuperMicro based system with 256GB RAM and ~450TB usable space, using AD as auth source.