Bug 11640 - file copy from Mac missing resource fork
Summary: file copy from Mac missing resource fork
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: File services (show other bugs)
Version: 4.1.0
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
Depends on:
Reported: 2015-12-10 23:45 UTC by Leo Liou
Modified: 2018-10-01 09:08 UTC (History)
2 users (show)

See Also:

smb.conf (4.23 KB, text/plain)
2015-12-10 23:50 UTC, Leo Liou
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Leo Liou 2015-12-10 23:45:25 UTC
opened on behalf of my customer.
the issue is when copying a set of font files from Mac (cli or drag-and-drop),
some of the files are NOT copied (file size=0).

for example,
the extended attribute ._<font> files are copied (4096 byte), 
but the <font> files themselves are not (although created). 

in samba log, I did not see any "real_write_file" for the target font file (for example, FrutiVCCP57RmCn), but what is strange is that some did work (Arial.ttf).

in network trace, I did not see "write andx" for the files either (did see them for the ._<font> files though).  

I wrote this off as issue with the Mac client, but customer claim no issue with such copy with windows file share; so he thinks the issue is with Samba server (3.6.25). 

any guidance on this issue would be greatly appreciated.
Comment 1 Leo Liou 2015-12-10 23:49:19 UTC
I have network trace (87M) that I can provide for debugging purpose, but too large to attach here. 
how should I proceed?
Comment 2 Leo Liou 2015-12-10 23:50:24 UTC
Created attachment 11705 [details]
Comment 3 Steve French 2015-12-11 00:00:12 UTC
You describe this as copying files from Mac to Samba not copying files using the cifs vfs (cifs.ko) ie not using the Linux cifs/smb3 client but rather the Mac client.

If you suspect a bug in the client, you should open a bug against Apple, if server then you should open it against Samba file server.

In addition, it is usually helpful to submit a network trace of the failure so developers can see what the Mac client (or Samba server) is doing wrong.

Comment 4 Steve French 2015-12-11 00:02:52 UTC
(In reply to Steve French from comment #3)
A network trace for the simplest file copy should be tiny (use a small file, and a small subdirectory).
Comment 5 Steve French 2015-12-11 00:05:27 UTC
Also make sure that you have Mac support properly configured including using vfs_fruit (the apple support module for optional mac features), and make sure you are using a reasonably current version of Samba (e.g Samba 4.1 or later, Samba 4.1 came out in 2013, Samba 4.3.2 is most current).

There are examples of discussions of vfs_fruit configuration on the mailing list e.g. https://lists.samba.org/archive/samba/2015-July/193012.html