Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.6: Force the sytem to use ._ resource forks in SMB mounts Network
Snow Leopard only hintI encountered an issue with a mounted SMB shared drive, where users have always put their files using Tiger or Leopard without any issues. Some software (in this case, ADI Chart) uses the resource fork to store information. In Snow Leopard, SMB mounts are set to use the xattr (extended attributes) feature instead of ._ files for storing the resource fork (a nice change; less clutter).

Unfortunately, this method is not backwards compatible, so our other users are unable to read files uploaded by 10.6, and our 10.6 users cannot read any files already on the server (uploaded by pre-10.6 systems). So, we need to disable this new feature.

It turns out to be related to the 'NTFS Streams' feature of SMB mounts, so if we disable those, then all is well. To do this globally (per machine), we need to create /etc/nsmb.conf, or add the streams line below to the [default] section if the file already exists:
#######
[default]
streams=no
#######
I used Terminal to make this change: sudo vi /etc/nsmb.conf.
    •    
  • Currently 3.04 / 5
  You rated: 1 / 5 (23 votes cast)
 
[14,364 views]  

10.6: Force the sytem to use ._ resource forks in SMB mounts | 2 comments | Create New Account
Click here to return to the '10.6: Force the sytem to use ._ resource forks in SMB mounts' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.6: Force the sytem to use ._ resource forks in SMB mounts
Authored by: deviantintegral on Dec 31, '09 07:35:11AM

Note that Samba doesn't support NTFS streams, so this will only affect you if you're writing to a Windows file server. There might be a way to disable streams on the server itself, which would cause OS X to automatically use ._ files instead.



[ Reply to This | # ]
10.6: Force the sytem to use ._ resource forks in SMB mounts
Authored by: fritza on Mar 12, '10 10:59:08AM

This is a life-saving hint. I have a question:

I'm repairing metadata and resource forks lost in an "enterprise-quality transfer" of files from Mac OS X Server 10.4 to a SMB share. Running rsync from the Mac server got me the ._files I needed, and using this fix shows the files as repaired. (Hint: Use Darwin Ports to install rsync 2.6.6 .)

However, the SMB share has been in use for some months (don't look at me, I was called in for rescue) since the enterprise-quality transfer, and I worry that metadata and resource forks have been written to it using NTFS streams. If we turn NTFS streaming off (at either end), will the new metadata/resources become invisible?



[ Reply to This | # ]