Basically SMB is faster, and feature rich in Windows file. rw-rw-rw- 1 guilherme users 13304 Sep 25 09:58 test\ file. SMB comes from the Windows world, and does not provide protocol features for macOS file system special features. DS_Storeĭrwx- 1 guilherme users 4096 Sep 25 09:35 MacBook\ Air\ de\ Guilherme.sparsebundle/ĭrwxrwxrwx 1 guilherme users 31 Sep 25 09:58 Test\ Folder# ls -laĭrwxrwxrwx 1 guilherme users 31 Sep 25 09:58. ĭrwxrwxrwx 1 nobody users 126 Sep 25 08:57. Only happens when connecting as a registered user from a Mac.ĭrwxrwxrwx 1 nobody users 58 Sep 25 09:57. Possible solution are to either go with separate EA stores for SMB and AFP, to delete all Dot Underscore files in close-to-realtime or to only use one protocol.Does this permissions issue still occur in the latest RC? Pretty sure the ownership problems are being caused by vfs_fruit. These applications either don’t work at all or have issues on such storages. The problem I described here is an issue by itself, however some applications depend on working extended attributes. However, if you try to read the same metadata over an AFP-mounted sharepoint it’s a completely different picture: The metadata is completely unusable. Up to this point, everything is as expected: We could access the metadata and it was exactly what we put in. $ xattr -w sh. 1234567890abcdef testfile #write EA Here’s an example executed on a mounted SMB sharepoint: If you write extended attributes using SMB and read the data over AFP it get’s scrambled. In theory now all OS X clients independently of the network protocol they use should have a consistent view. Thereby SMB and AFP use the Dot Underscore fallback. To do that I disabled netatalk’s native EA support ( ea = none in nf). The goal is that whatever network protocol you use you should always see the same data (including it’s metadata). However this post is about a very interesting problem that occurs only if you try to use a Linux server as a fileserver that exposes the same folder for OS X clients using SMB and AFP with extended attribute sharing. I described one possible way in my post Win & Mac: Clean Dot Underscore Files.
Many people including me have been bugged by this fallback and have searched for ways to remove those files. On filesystems that don’t support extended attributes OS X writes this data into Dot Underscore (._) sidecar files. Filesystems like JHFS+ that natively support this feature store this metadata completely hidden from the user. Extended attributes on OS X allow applications to store additional metadata along data files.
0 kommentar(er)
