FreeFileSync Forum

This scenario (same name, different case), for me, shows the same as yours. They are equal and action 'update' is to be taken. It says "Items differ in name only", but mine is categorized under updates, not a conflict. What version of FFS are you on?


I'm on version 13.7.

FWIW, after the sync ...

You can mouse-hover over the middle grid to see the details. Zenju, 25 Aug 2024, 07:33

Thanks for the reply!


By "middle grid" I presume you mean the outlined area below, yes?
When I mouse over the outlined area, I get nothing.

What am I misunderstanding?

This morning when I made my weekly FFS run (unidirectional, with moving changed target files to a different location for versioning), FFS reported one conflict, but it was for a folder, not for a file.

I don't understand when a folder might throw a conflict. Perhaps if I do something such as change ...

It amazes me how popular Apple still is when they are the most anti-consumer and anti-convenience developers ever... smh


I agree wholeheartedly that Apple is “anti-consumer, and anti convenience." I would only quibble with describing it as “the most“…

It seems to me that there is a pattern ...

Aaah...never mind! It was a security issue. Apparently FFS is not from a "known developer," and instead of giving a straightforward error message to that effect (the way previous OSs did) in Ventura Apple just says the app is "damaged." On the Privacy and Security section of System Settings I had ...

I just upgraded from macOS Monterey to Ventura, and FFS no longer opens. I redownloaded the Donation Edition and reinstalled it, but I still get the same error message. I am running FFS 13.0.

Any thoughts about how to fix this?

Sounds good. Thanks for all of your help!

My biggest sync.db file is about 1MB, super small, and I was just assuming you had at least that much space :p

I DID have that much space, enough to save the DB file for 2 FFS runs (source = different folders). I didn't run out of the space until the 3rd run.

Thanks for all of your help. I ...

OK, digging even further. The FFS database file is stored on the SOURCE, not on the target, it seems. My first two runs ran perfectly, and then subsequent runs errored out with the "not enough space" message. Sure enough, if I look at the sources (they are folders, not an entire volume), the first ...

As I continue to dig into this and observe what is happening, it seems that the copy job always fails at the very end. If I select "Ignore," the job ends and reports the error in the log. As far as I can tell, all files have been copied.

I've noticed that the temporary file that causes the error ...

Thanks for your thoughts. Here's the scenario I ran into a while back (I wasn't using FFS for this). The images being copied are photos managed by Lightroom. I was trying to export some photos from LR that were about 5 years old, and two of them wouldn't export. When I opened them up in Lightroom ...

Thanks for the quick reply and for the info about how FFS generates the tmp files.
As requested, the screenshots are attached.

The destination volume has 2.85TB free space (out of 3TB). I suspect the temporary file isn't bigger than that! :)

My goal is to have FFS make an archive of photos I have ingested from cameras, phones, etc. The purpose is to protect against accidental deletion of source photos (idiot user error) as well as to protect against "bit rot" (no user error, but a photo becomes either unreadable or readable but ...

I set up FFS in Update mode with versioning. On the second run, FFS threw this error:
Cannot write file "/Volumes/LR Managed Folders MPG BU/2014-09-24_MBG Snapshot 09-08-2018 Thu 11-45 AM/.sync.ffs_db.3e33.ffs_tmp".

ENOSPC: No space left on device [fcntl(F_PREALLOCATE)]

If I understand this ...

Indeed it will do it! Thanks for the help.

What I want to do is to set up a one way copy/backup job that works like this:

- If a file is on the source but not on the destination, copy the file to the destination

- If a file is on the source and is already on the destination, do NOT copy the file, even if the file on the source is newer or ...