:2e* and .AppleDouble files when using AFP

[martinjk]

I have a problem using my Mac with the TS239P. I'm running the latest firmware 3.1.1 Build0815.

When accessing the network drive from the Mac using AFP a lot hidden files are created on the NAS. As long as I use Mac only it is not that big of a problem since the files don't show up in the Finder. When I connect from my windows machine using Samba I see a lot of funny filenames.

When I directly connect to the NAS using ssh I see that the filenames / directories are named either :2e* or .AppleDouble.

I managed to prevent the creation of .DS_Store files by changing the network behavior on the mac itself:
defaults write com.apple.desktopservices DSDontWriteNetworkStores true

Is there any known way to prevent these files from beeing created?

[schreibe]

Hello,

I had the same problem and solved it by adding veto files to the smb.conf file. I think this :2e_ File were needed by netatalk to store some extra Information. By adding the Files to veto files, they will not shown anymore to a windows machine.
Because the smb.conf will new generated by starting the windows server I edit the start script like following:
-Log in by ssh!
- edit the file /etc/init.d/smb.sh

you find following line:
/sbin/setcfg global "veto files" "/.AppleDB/.AppleDouble/.AppleDesktop/:2eDS_Store/Network Trash Folder/Temporary Items/TheVolumeSettingsFolder/.@__thumb/.@__desc/:2e_*/" -f ${CONFIG}

i add the red item

after that you only have to restart the windows server (by the admin webinterface) and these File should disappear.

Hope this helps.

Greeting.

Manfred

[martinjk]

Thanks, that's working. However the changes seem to get lost upon a full server restart.

Any idea how to make these changes permanent?

[James.W]

hi guys,

thanks for the report, we will fix this in the next release. : )

James

[schreibe]

So here is what i found about that issue:

These Files are Resource Forks from Mac OS X. Normally they should not appear because Netatalk (the afpd Daemon) stores them under the AppleDouble Directory. But it seems that Netatalk has a Probleme with Snow Leopard (or Snow Leopard with Netatalk). It tries to store extra Information in the ._ File.
An Example:

Take a downloaded File:

iMac:Downloads manfred$ xattr TheUnarchiver2.1.zip
com.apple.quarantine

copy it to a Share:

iMac:Public manfred$ xattr TheUnarchiver2.1.zip
com.apple.FinderInfo
com.apple.quarantine

When you delete the corresponding ._ File ist looks like that:

iMac:Public manfred$ rm ._TheUnarchiver2.1.zip
iMac:Public manfred$ xattr TheUnarchiver2.1.zip
com.apple.FinderInfo

i tried the same with Leopard and these ._ File did not appear.

There is an threat about that in the netatalk maillinglist. So I think this issue will be fixed with a coming release.
The vetofile fix is a quick fix for that, but perhaps not the best solution, because Snow Leopard and netatalk are creating 4 File on the Filesystem:

The Datafile, the resource fork, the appleDouble for the datafile and the appleDouble for the resource fork (both in .AppleDouble).
When delete all File and then Copy the same File with Leopard (also downloaded form the Internet), you only get two files:
The Datafile and the AppleDouble (in AppleDouble).
I think there will be also Problemes between Snow Leopard and Leopard, when you move a File over Netatalk (Qnap share).

So i hope this issue will be fixed with the next firmware Release from Qnap.

I've got the Qnap TS 119 with Version 3.1.2 build 1014T.

Greeting Manfred

[schreibe]

Hi martinjk,

here is a solution to make the changes permanent:

Make a StoreDirectory:

Code: Select all

mkdir /share/HDA_DATA/.storedConfig

Copy your edited /etc/init.d/smb.sh to that place:

Code: Select all

cp /etc/init.d/smb.sh /share/HDA_DATA/.storedConfig

There is a place where you can putt Script which will be started at startup (autorun.sh). You find an Wiki at http://wiki.qnap.com/wiki/Autorun.sh.
The next line is for the TS-119 and perhaps you have to modify (Wiki).

Code: Select all

mount -t ext2 /dev/mtdblock5 /tmp/config

Code: Select all

vi autorun.sh

(it don't mind if this file doesn't exist)

Write following in this file:

Code: Select all

#!/bin/sh

/etc/init.d/smb.sh stop
/bin/cp -f /share/HDA_DATA/.storedConfig/smb.sh /etc/init.d
/etc/init.d/smb.sh start


After that you have to make this file runnable and umount the /dev/mtdblock5 dev :

Code: Select all

chmod 755 /tmp/config/autorun.sh
umount /tmp/config


Now it should work.

If you change something on the samba server (webinterface) you probably have to copy the new /etc/init.d/smb.sh to the storedConfig Dir.

Greeting

Manfred

[martinjk]

Manfred,
thx for your detailed description. I have made the config changes and everything is working fine now.

Hopefully QNAP provides a fix for the Snow Leopard problem.

Cheers,
Martin

[Reinhard]

hi guys,
thanks for the report, we will fix this in the next release. : )

James

Is there any news on this issue ?
Is it fixed with FW Release 3.1.2 Build1207 ??

Would be nice to have an update.

Thanks,
Reinhard

[TryWait]

hi guys,
thanks for the report, we will fix this in the next release. : )

James

Six months after this was posted by qNAP support, I am running 3.2.4 and this issue is not fixed. I just got this TS-419P up and running and these resource fork files are a big pain.

[occamsrazor]

I just bought a TS-239 Pro II and have the same problem, and don't know what to do, the littering of these files everywhere makes navigating through e.g. the Web File Manager etc really ugly...

Should I try to disable their creation using one of the methods mentioned, or using Tinkertool etc?
Does the same problem occur when copying files via SMB? Should I just use that instead?
How soon can we expect a real fix?

[schreibe]

This is not really a problem of Qnap - it is a problem of netatalk. Netatalk is the afp-fileserver used in your NAS similar to samba / cifs. My posted solution is only a hack, so that you can't see the ugly files on windows. I just tested the new version of netatalk (2.1beta2) and it seems that the problem with the xattributes used in Snow Leopard is fixed. So i hope this issue will be fixed in the next release. I hope Qnap will fast provide a version with the new netatalk distribution as soon as there is a stable version of it. In the meantime you have to fix it with my proposed solution / hack. You can also use only smb, but then you see the same File with ._ in front of the name. This is because Snow Leopard stores the xattributes in that file.

[occamsrazor]

So is my understanding right that currently Netatalk is actually creating a bunch of invisible files in the wrong place, that ought not to be created?

As regards the "current situation" vs your hack vs using SMB - is there a difference in what "ugly" files are actually created and where, or just what files are shown to the user?

I just bought this NAS and was planning to copy over all my movies and music, around 1.5TB, but now I'm hesitant to even do anything yet if it's going to create a whole load of extra invisible files that I'll struggle to get rid of in the future... All I want is to see the same "real" files whether I connect via Web File Manager, AFP, SMB, etc... this seems like it ought to be pretty basic/core functionality.

[occamsrazor]

Please could someone from QNAP advise on the status of this, or what is recommended to do?
I've got this brand new device gathering dust because I'm hesitant to dump all my files on it for fear of creating a whole bunch of unnecessary invisibles that I've no idea how I'll be able to get rid of later....

[gsarbia]

Does the same problem occur when copying files via SMB? Should I just use that instead?

I've always been using SMB since AFP before 3.2.5 was broken on ARM processors, and I've never seen such a problem. The only limitation I've found so far was related to some files causing paths to be too long. There are also minor annoyances like an inconsistent behaviour when calculating folder sizes, but the core functionality (hardly rocket science, i.e. read file, write file) is there when using SMB from Macs.

Best regards,
Giovanni

[dfeist]

I just tested the new version of netatalk (2.1beta2) and it seems that the problem with the xattributes used in Snow Leopard is fixed..

Did you update netatalk or your Qnap device or an another linux box?
If it was on your Qnap device is there any chance you provide some details about how you went about this update?

thanks,
Dan