Samba4.x - Can anyone provide a working smb4 config for macOS extended attributes?

[johnd]

Hi.
I'm running a FreeBSD 14.3 server with UFS2 and samba419 (also tried samba420). We've got some macOS (tahoe) users who store files on this server and they want to use macOS extended attributes. In general, this works, but for every file on the filesystem, there is an additonal file prefixed with "._" (dot-underscore). This is an AppleDoube file holding the extended attributes.

Have anyone got it working without these annoying ._files? I'm pretty sure there is a way to store the extended attributes in the file itself, without havig all these AppleDouble files.

I've tried some configurations, mostly ending up that the users can't store anything on the share anymore.

Thank you!

 

[SirDice]

I'm pretty sure there is a way to store the extended attributes in the file itself, without havig all these AppleDouble files.

fruit:resource = [ file | xattr | stream ]

Controls where the OS X resource fork is stored.

Due to a spelling bug in all Samba versions older then 4.6.0, this option can also be given as fruit:ressource, ie with two s.

Settings:

file (default) - use a ._ AppleDouble file compatible with OS X and Netatalk

xattr - use a xattr, requires a filesystem with large xattr support and a file IO API compatible with xattrs, this boils down to Solaris and derived platforms and ZFS

stream (experimental) - pass the stream on to the next module in the VFS stack. Warning: this option should not be used with the streams_xattr module due to the extended attributes size limitations of most filesystems.

vfs_fruit

Yes, it can be turned off, but stream has some limitations and xattr really requires ZFS, not UFS.

 

[vmisev]

Ha, IDK about vfs_fruit, thanks SirDice
I always (since 2001) did this with netatalk and samba set to share same dirs, Mac clients connecting to netatalk and Win clients to samba.