I’m encountering a problem when importing recordsdata from an exterior onerous drive formatted as ExFAT. For each file I add by Google Chrome, a second file with the identical identify is created, prefixed with ._ and with a dimension of 4KB.
Right here’s the important thing element: The ._ recordsdata usually are not seen on the exterior drive earlier than the add (I’ve enabled hidden recordsdata visibility to examine this).
They solely seem after the recordsdata are uploaded.
My understanding to this point: I do know that macOS creates ._ recordsdata to retailer metadata (like useful resource forks or Finder attributes) on file programs that don’t natively assist macOS metadata, reminiscent of ExFAT. Nonetheless, on this case, I’m not copying these metadata recordsdata manually, and so they don’t appear to exist on the drive earlier than the add course of begins.
My query: Why are these ._ recordsdata being created through the add course of if they don’t seem to be seen nor chosen beforehand on the drive?
Extra context:
- My exterior drive is formatted as ExFAT for compatibility with each macOS and Home windows.
The recordsdata being uploaded don’t appear to have any particular Finder attributes, tags, or customized icons (no less than so far as I can inform). - Once I add recordsdata to Google Drive utilizing Google Chrome, both by dragging them from a Finder window to the drop space within the browser or by utilizing the “+ New > Folder add” possibility within the Google Drive internet interface, a second file with the identical identify is robotically created for every uploaded file. These further recordsdata are prefixed with
._and have a dimension of 4KB.
I’d recognize any insights into why this would possibly occur and sensible steps to resolve or stop it!
