Finder fails to write to SMB share yet Terminal successfully performs action

Originator:broccardo
Number:rdar://7899235 Date Originated:4/23/2010
Status:Open Resolved:
Product:Mac OS X Product Version:10.6.3 build 10d573
Classification:Serious Bug Reproducible:Always
 
Summary:
When connected to a SMB share hosted by a Linux server using Samba version 3, user can not successfully write files to the share using drag and drop in the Finder. The same user can successfully use Terminal.app to move or copy those same files to the share.

To Reproduce:
[Need Linux based server hosting a file share via SMB. Permissions to files and folders are controlled via ACL. User has an account with permissions to read and write files to that share or a specific subdirectory.]
1. Connect to the share, authenticate and mount the share.
2. Open a Finder window with view of share.
3. In the Finder, attempt to copy a file (file type does not matter) via drag and drop method from the Desktop to share.

The file, as user has read/write access, should successfully copy to the share, but it does not. The Finder cursor displays a prohibitory sign.

4. With server connection still active, open Terminal.app
5. In Terminal.app, use the cp command to copy that same file from the Desktop to the share.
 > cp /Path/To/File /Path/To/Server/

The file should copy successfully.

As exhibited by using Terminal.app, the user does have proper access to the share, but the Finder is misinterpreting those permissions and preventing proper use.

Additional information:
- Files that already exist on the share can be properly edited in their appropriate applications and all changes are saved.
- If a new directory is created on the share and you attempt to drag and drop copy files from the Finder to the new directory, Finder errors with a -36 error.

Comments

setting the samba configuration variable "posix locking" to "no" will allow files to be written to the share via finder. However, it is clear that this should not be necessary ("you should never need to change the default behavior"), and it is not clear what the worst-case consequences are of disabling posix locking. This issue is still present in 10.6.6.

By pol.llovet at March 18, 2011, 7:52 p.m. (reply...)

Issue not corrected by final production version of 10.6.4.

By broccardo at June 21, 2010, 7:55 p.m. (reply...)

Also discussions at http://serverfault.com/questions/109879/os-x-finder-error-36-when-using-smb-shares-on-a-samba-server-bound-to-ad

By shay.telfer at June 2, 2010, 2:45 a.m. (reply...)

Appended to ticket

See also this thread and reference to rdar://6521274 http://discussions.apple.com/thread.jspa?threadID=1776934

By broccardo at April 23, 2010, 3:12 p.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!