SOLVED Copying Large files results in "._" files of 4096kb AS WELL as the correct file

Status
Not open for further replies.

melvynadam

Cadet
Joined
Apr 12, 2013
Messages
2
I am using my FreeNAS box (FreeNAS-8.3.0-RELEASE-x86 (r12701M)) as a backup server for my media server.

Using my MacBook Pro, I just copied a large folder (70GB) of material from my QNAP NAS to the FreeNAS box.

The source folder looked something like this:
S01E01.avi 185MB
S01E02.avi 185MB
S01E03.avi 185MB

The resulting folder on my FreeNAS looks like this:
.@__thumb <Folder>
._.@__thumb 4,096K
._S01E01.avi 4,096K
._S01E02.avi 4,096K
._S01E03.avi 4,096K
S01E01.avi 185MB
S01E02.avi 185MB
S01E03.avi 185MB


What have I misconfigured on the FreeNAS or is this somehow caused by using MacOS for the copy operations?
 

JaimieV

Guru
Joined
Oct 12, 2012
Messages
742
Re: Copying Large files results in "._" files of 4096mb AS WELL as the correct file

The ._ files are a Mac thing, they're emulating HFS+ features in a non HFS+ filesystem. Delete them if you like, they're completely disposable: all they hold is previews and metadata which you won't care about. Info here.

4096K is very different to 4096mb as in your thread title, though!

/Edited to add: Mind you, I don't get these on my NAS when I copy movies to it. Are you certain they're not generated by the QNAP?
 

melvynadam

Cadet
Joined
Apr 12, 2013
Messages
2
Re: Copying Large files results in "._" files of 4096mb AS WELL as the correct file

The ._ files are a Mac thing
Thanks. Even though I thought it unlikely that the Mac was the cause, I included that info to be as comprehensive as possible. Will delete them.

4096K is very different to 4096mb as in your thread title, though!
100% right but I can't see how to edit it now :(

/Edited to add: Mind you, I don't get these on my NAS when I copy movies to it. Are you certain they're not generated by the QNAP?
Well they're not on the QNAP in the source folders and if I copy a folder to my Windows box, using Windows, those files don't appear. So it looks like the Mac is the problem.
 
Status
Not open for further replies.
Top