Apple double files `._*` are always uploaded when mounting with Mac Fuse-T

What is the problem you are having with rclone?

I am using Fuse-T on the Mac 15.2 and mounted Pikpak. I always get the Apple double files ._* for when putting any file into the mounted folders.

Below the Fuse-T config in /Library/Application Support/fuse-t/cfg/fuse-t.ini.

[Default]
namedattr=false
backend=smb
noatime=true
nomtime=true

Both backend=smb and backend=nfs have the same behaviour.

List of files on mount folder.

>>> ls -la
total 127
drwxr-xr-x  1 USERNAME  staff  16384 23 Jan 20:50 .
drwxrwxrwx  1 USERNAME  staff  16384 23 Jan 20:49 ..
-rw-r--r--  1 USERNAME  staff   4096 23 Jan 20:50 ._gold 1M others 1000.txt
-rw-r--r--  1 USERNAME  staff   4096 23 Jan 20:50 ._gold.txt
-rw-r--r--  1 USERNAME  staff   4096 23 Jan 20:50 ._hp.txt
-rw-r--r--  1 USERNAME  staff   4096 23 Jan 20:50 ._mj.txt
-rw-r--r--  1 USERNAME  staff   4096 23 Jan 20:50 ._qty.txt
-rw-r--r--  1 USERNAME  staff   4096 23 Jan 20:50 ._sp.txt
-rw-r--r--  1 USERNAME  staff   4096 23 Jan 20:50 ._toggles.txt
-rw-r--r--@ 1 USERNAME  staff    340 23 Jan 20:50 gold 1M others 1000.txt
-rw-r--r--@ 1 USERNAME  staff    222 23 Jan 20:50 gold.txt
-rw-r--r--@ 1 USERNAME  staff     62 23 Jan 20:50 hp.txt
-rw-r--r--@ 1 USERNAME  staff     62 23 Jan 20:50 mj.txt
-rw-r--r--@ 1 USERNAME  staff     61 23 Jan 20:50 qty.txt
-rw-r--r--@ 1 USERNAME  staff     80 23 Jan 20:50 sp.txt
-rw-r--r--@ 1 USERNAME  staff     81 23 Jan 20:50 toggles.txt

I also asked on Fuse-T repo, but the author also found it strange.

Run the command 'rclone version' and share the full output of the command.

rclone v1.69.0
- os/version: darwin 15.2 (64 bit)
- os/kernel: 24.2.0 (arm64)
- os/type: darwin
- os/arch: arm64 (ARMv8 compatible)
- go/version: go1.23.4
- go/linking: dynamic
- go/tags: cmount

Which cloud storage system are you using? (eg Google Drive)

Pikpak

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone mount Pikpak: /Users/USERNAME/Cloud-Drive/Pikpak \
 --allow-other \
 --vfs-cache-mode full \
 --no-checksum \
 --buffer-size 512M \
 --dir-cache-time 1h \
 --allow-non-empty \
 --drive-chunk-size 2G \
 --vfs-cache-max-size 80G \
 --vfs-disk-space-total-size 90G \
 --cache-dir /Users/USERNAME/Cloud-Drive/rclone_tmp/cache \
 --cache-tmp-upload-path /Users/USERNAME/Cloud-Drive/rclone_tmp/upload \
 --vfs-read-chunk-size 256M \
 --vfs-read-chunk-size-limit off \
 --vfs-fast-fingerprint \
 --use-server-modtime \
 --no-modtime \
 --rc \
 --rc-no-auth \
 --rc-serve \
 --transfers 10 \
 --use-mmap \
 --progress \
 --poll-interval 0 \
 --rc-web-gui \
 --no-console \
 --noappledouble \
 --noapplexattr

I also tried including -o nonamedattr -o nomtime -o backend=smb -o noappledouble and got the same results.

welcome to the forum,

try --noappledouble

Thanks for being so quick! I tried it and it's the same result. Just updated the post content.

no worries, here comes @kapitainsky

those are not rclone flags

IMO it is no rclone nor FUSE-T issue. This is how macOS works. If there is any metadata and target filesystem (which is the case for mounted smb or nfs) does not support it directly then macOS will store it in sidecar ._ files.

Until this issue is fixed:

I am not sure anything can be done.

Thank you @kapitainsky . What's strange is that Apple double files are not upload when I use macFuse or rclone nfsmount. So the problem is very isolated to Fuse-T... Trying all combinations and the behaviour is still replicable.

You are correct - these are configs for Fuse-T in /Library/Application Support/fuse-t/cfg/fuse-t.ini.

I would consider it a bug with nfsmount:slight_smile: At least by default I would expect my mount to save everything OS asks it to.

But I do not see why not to have an option to filter it out when user wants.

Also these sidecar files are tiny and they serve some purpose. At least as long as you use macOS.

Good point! Let me test if ._* is ever generated on nfsmount....

Just tested - mounted the drive and put a file in Finder.

  • When mounted using rclone nfsmount or macFuse, ._* file is not generated at all
  • But the file is generated using Fuse-T with either smb or nfs backend.

I guess this behaviour is driven by how the mount is triggering the Apple double?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.