I am a new user of FreeFileSync (ver 11.13), venturing into NAS. I just bought a Synology DS220j, connecting to a fairly new Macbook Pro using my home wi-fi network. The file system for the Synology box is ext4.
I see there are a few posts about problems with .ffs_tmp files, but I didn't see one about this error.
A mirror batch job from the Macbook to the Synology NAS yielded six errors for the same folder, all of the form
"Cannot write file /Volumes/NV/CLapN/Art/MyArt/ArtProjects/WiP_Eureka/PrintingAndInstalling/ForDesigner/Names_and_PottedBios/Morse_Initials/JV~2c58.ffs_tmp".
EISDIR: Is a directory [fcntl(F_PREALLOCATE)]
NV is the NAS volume on the Synology box.
The folder Morse_Initials had 65 files, all with names like JV.tiff. The six that yielded error messages were not copied to the NAS, but the other 59 were.
After the batch job had finished, using the MacOS finder I could not see any files or folders ending in .ffs_tmp in the Morse_Initials folder in the Mac or in the folder on the NAS. (I turned viewing hidden files on, but there weren't any of those in either folder).
I ran the batch job again. This time it copied five of the files it missed the first time, but generated the same error for the sixth.
I am running FreeFileSync from an administrator account on the Macbook.
On the forum have seen two suggested things to do:
- disable fail-safe file copy (which I see is an option in the Preferences)
- exclude *.ffs_tmp
But I do want to know if files are not copied.
Any advice?
.ffs_tmp error - EISDIR: Is a directory
- Posts: 2
- Joined: 10 Sep 2021
-
- Posts: 4867
- Joined: 11 Jun 2019
Looks like it's trying to preallocate space for a directory instead of the file... I don't know if that is something Zenju would need to change or if it is a fault of the NAS. You can disable fail-safe file copy, that may or may not fix it. This would technically increase risk of data loss, as this feature waits until the file transfers fully before deleting the existing copy. Excluding the ffs_tmp files won't do anything
-
- Posts: 2946
- Joined: 22 Aug 2012
Never had this problem running syncs to either of my Synology NAS-ses or between those NAS-ses.
But, that has always been when running FFS on a Windows machine.
So, it seems either a MAC-OS related issue, or a FFS (MAC-version) related issue.
But, that has always been when running FFS on a Windows machine.
So, it seems either a MAC-OS related issue, or a FFS (MAC-version) related issue.
- Posts: 2
- Joined: 10 Sep 2021
Well, this happened about the first time I tried to use FreeFileSync, and it hasn't happened again, so I can't reproduce it. It was also about my first experience with using NAS.
I don't know if this is related, but I have found that if I have a single folder with a large number of files directly in it (i.e. not in subfolders), then a mirror sync to the Synology NAS often fails. ("Large" in this case meant over 10,000 - they were frames for an animation.) I suspect that the problem is at the NAS end and is something to do with the way it responds (or doesn't respond) to the request from macOS to list the files in the directory, or something like that. If so, it isn't FreeFileSync's fault.
I don't know if this is related, but I have found that if I have a single folder with a large number of files directly in it (i.e. not in subfolders), then a mirror sync to the Synology NAS often fails. ("Large" in this case meant over 10,000 - they were frames for an animation.) I suspect that the problem is at the NAS end and is something to do with the way it responds (or doesn't respond) to the request from macOS to list the files in the directory, or something like that. If so, it isn't FreeFileSync's fault.
