Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
FAT32 can go into the Tb, but the cluster size gets bigger. Something like 16Tb is the limit, and 2Gb files size.

exFAT allows more disk and file size that you'll ever own in the next 10 years (or more), works in both windows (newer windows) and mac (newer OS X).

No problem if copying NTFS drive data on to a mac.
Copy back to a windows based system can be a problem as the mac allows longer path + filename lengths. Windows can read them, just not write them for some odd reason.
 
Hmm okay. Isnt FAT limited to 4GB file size though? I Would definitely want it to be optimized for Mac first and foremost as that will be majority interaction.

In line with this I guess, will I run into any potential issues when transfering NTFS data to OS X Extended (Journaled)?


You can use exFAT that overcomes that 4GB file size limitation. Just be aware exFAT is not a journaled file system, so is less stable that NTFS or HFS+.

You should have no issues moving data from a NTFS drive to a HFS+ (Mac OS Extended) drive.
 
  • Like
Reactions: tennisproha
You should have no issues moving data from a NTFS drive to a HFS+ (Mac OS Extended) drive.
One more thing. On one of my external drives I have files that were originally on a work Mac. I transferred these files to my external HD. Now I wanna transfer them back to my personal Mac.

The files have hidden counterparts that usually have the same file name except with symbols added to the name. What are these and what should I do with them?
 
They don't matter, it's just the spotlight or preview stuff. The mac will recreate them.

I wish there was a way for the mac not to copy them on to external drive as it's a pain if windows is set to show hidden files.
 
One more thing. On one of my external drives I have files that were originally on a work Mac. I transferred these files to my external HD. Now I wanna transfer them back to my personal Mac.

The files have hidden counterparts that usually have the same file name except with symbols added to the name. What are these and what should I do with them?
I assume the external is not formatted in HFS+. What happens when you copy some files from a Mac drive formatted in HFS+ to a non-HFS drive is that file format cannot handle the resource forks and meta data in the files, so that data gets put in a separate file of the same name prepended with ._. That is likely what you are seeing and is nothing to worry about.
 
That is likely what you are seeing and is nothing to worry about.
So when I transfer these files back to a HFS+ drive, what will happen to these .dot files? How does OS X handle the import; re-merges or deletes or leaves these files?

From what I've read online just now I can delete the .DS_Store files via Terminal as these are mostly view options setting from the previous Mac they were on. As for the ._. appledouble, apparently I can use the dot_clean command to merge the resource fork back within the data fork?

Although, I'm not clear on the exact Terminal commands as they are typed out slightly differently on different sites. I'd like to do this as it is just one set of files and therefore once done, there'll be continuity throughout the system! I'd appreciate the proper commands if anyone could help.
 
Last edited:
Also, Is there a way to sandbox (just isolate) the external HD files when I transfer them to the system HD?
 
So when I transfer these files back to a HFS+ drive, what will happen to these .dot files? How does OS X handle the import; re-merges or deletes or leaves these files?

From what I've read online just now I can delete the .DS_Store files via Terminal as these are mostly view options setting from the previous Mac they were on. As for the ._. appledouble, apparently I can use the dot_clean command to merge the resource fork back within the data fork?

Although, I'm not clear on the exact Terminal commands as they are typed out slightly differently on different sites. I'd like to do this as it is just one set of files and therefore once done, there'll be continuity throughout the system! I'd appreciate the proper commands if anyone could help.

Here is Apple's documentation on the dot_clean command. Basically you just run dot_clean followed by the path to the folder.

Follow this... in Terminal enter "ls /Volumes" (without the quotes). That will show all mounted volumes including your USB key. So in that list say you see your UEB key named mystuff. Then the path would be /Volumes/mystuff. So the full command would be "dot_clean /Volumes/mystuff" (without the quotes).

The hidden files will not copy back to HFS since they are hidden and you will not have been able to select them by a normal Finder select and drag/drop.
 
  • Like
Reactions: tennisproha
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.