FreeFileSync Forum

2 additions to my suggestion:

If a Compare run should reveal that the "bottom line" of syncing
would exceed free space on dest: Pop a message box and...

If a Compare run should reveal that at some point of the Sync process
(replacing small files by larger ones, generating tmp files etc.)
there ...

It would be useful to know before (and maybe also after) starting Sync,
the "bottom line"/ resume/ balance of doing sync:

Bytes added - bytes deleted.
(Including the difference of the (to be) replaced files' size).

Benefit:
Before Sync:
I can tell if free space on destination suffices.
After Sync ...

I don't think it's a good idea to show important information (as base folders is)
only when hovering at them.
However I wonder why you didn't give that simple answer at first place.
Instead abatement... again.

OK, now I see why "Relative path" is empty in some cases.

But the main problem remains:

I do not know where the to-be-changed item is from/
which item is meant. And that is the important information.

Here we are:

2nd last line: I deleted GitHub-Link from desktop
Last line: bookmark backup file deleted by FF

Both belong to 2 different sync-pair items.

For both it is not shown which dir they belong to.
Which is important for to-be-deleted files.

So you're actually telling me I oversaw that?
You shouldn't take users being dumb.

I'm adressing the sync pairs where base location and relative path are different.

To know which files will be deleted then,
you have to check the dest dir (right column)
and identify the corresponding sync pair in ...

I have several directories defined for syncing.
Two of them are
the Desktop (c:\users\<username>/Desktop) and
FireFox' subdir bookmarkbackups.

After doing "Compare" the column "Relative Path" is empty for them
(eventually if just showing the to-be-deleted).
So I don't know the source directory of ...

If course it's "my fault" - never denied that.

I (and obviously not only me) wanted to point that it would be a desireable behaviour of FFS
if it would point me if entering bad values.
Tha's what a good app does - especially if it's at such important matter as syncing is.

@Plerry:
I get the ...

Works as designed.Zenju, 15 Sep 2025, 09:13

Well... then the design is bad in that matter.

May I ask you to have a look at the posts from users above?

Can you please tell what the .run installation for Linux does exactly, please?

I'm at openSUSE Leap.

Is root privileges necessary?
Are existing dependencies touched in any way?
Does uninstall work correctly (due to libs/ dependencies etc.)?

Do you provide signatures/ hashes for the .run file?

Typo in:

... (In my (most simple) case there is: SEQ = SEQ^(2n) meATffsForum, 06 Jul 2025, 10:55

Correct:
SEQ^(2)=id

Thank you for your reply.
However you're wrong:

Unless you disabled that, FFS already warned you that there is an overlap between one or more of your sync locations.

I din't disable the warning, but FFS didn't warn me (at 1st syncing).
That's what I wrote already in section "What would I ...

Minimal example:
2 folder pairs
1. d:\source1 d:\destination
2. d:\source2 d:\destination
Both source directories contain one distinct file respectively.

What would I expect?
Execution of 1st folder pair would make destination like source1.
Delete everything on destination, add file from source1 ...

You're making it exciting... :)
What behaviour of FFS is caused by what situation then?

Thank you for the test.

However actually that issue isn't due to user's experience, but algorithm-wise.
(As I wrote: for the devs).

I wrote: "... relative long...", with the focus on " relative ".

Iterating and filtering a 200K list to identify 1 file where the name
is known already will take a ...

Shall your post have anything to do with my question?

Devaluating a well reasoned and explained proposal... that's all?

People make mistakes.

For one of my programs long ago I did the fun to code a full constistency
check for source, dest and filters.
(However it was far a completely different problem) .

Although I was the author; was careful, and knew about the inconsitencies
that can happen... from time to time ...

Finally I understand what you mean.
Thanks for you endurance! :)

So I got it.
That is a way to use an affected sync object for filtering.

However... (sorry :) )
doing that way is not intuitve.
Building a synchronization setting I enter a source/ dest pair
and also the corresponding filter settings ...

You don't seem to understand - talking about something complete different.

You're explaining a way to do something that doesn't has anything to do with what I described.

Take my example.
However I stop at this point.

We're talking about the Filter dialog don't we?

I don't see how it should be possible to enter directories there other than
editing it by the hand. It's not there.

Please explain.

Let's take the example:
I included a source directory:
D:\test\source
And now I want exclude it's sub dir \23po ...

... show up as unexpected Compare results

Please excuse, I wasn't aware that you have in mind which kind of Compare results should show up .
;)

Hey, we're talking about large numbers of different files in different directories.
How should I know that somewhere I made an error in the filter ...

Yes, as you wrote:

After manual edit and after running Compare.

I wouldn't call that "elimation the possibility of misspelling/ typos".
That is close to nothing compared to what I propose.

Thank you for you reply.
However I know all that.

Actually you didn't get my point.
It's about implementation effiency when synchronizing.
(It's a question/ suggestion for the devs.)

When I need only one (or few) files from a source directoy that contains
ten thousands of files, my guess is that ...

It would be a help to prevent errors in the important task of syncing,
if FFS could make some consistency checks in the filter dialog at some point :

File Size
Allow only non-0 intervals (between Minimum and Maximum)

Include/ Exclude
Same entry in include and in exclude
Double entries
... (there ...

i.e. "Drag and Drop" and <Browse>-Button.

This isn't due to comfy in first place,
but to assist to prevent accidental misspelling.
A small misspeling might not be noticed (most times it isn't, is it?),
and might lead to drastical effects.
(Syncing is an important operation).

So not as a "Feature ...

The title might hint to where my question, suggestion, inspiration points to:

Using the info of journaling/ logging filesystems might speed up the application
(at least in identifying the changes).

...?

If I need to synchronize a unique non-directory object, say a file.
If I get it right, I have to add the including directory and
add an include filter for that; containing the filename.
Correct?

In my case there are directories with 10,000s of small files (process data),
where I need to synchronize ...

FFS warns if the contents of the left and right base location is substantially different.

What is "substantially different"?
When does FFS warn: before syncing, or after?

For these sort of cases, FFS provides Versioning.

I know about Versioning - it's something I don't need usually.
What I ...

I think my description (and header) needs clearification?

As far as I understand "Fail-save copy" helps for special (hopefully rare) situations
when something terrible happens and the copy of a file could not carried out.

My question is:

If FFS is still alive, what does it do then?
- Is further ...

I'm sorry - I made too few words as I thought it would be obvious ;)

The reason for the option:
If some source file has been unintentional, accidental or with evil intent
altered in a way that it's size is much less then the mirrored version,
FFS could help by giving a message before overwriting ...

Thank you for your detailed reply.

I think I understand the concepts of FFS and RTS now
(already having found the RTS manual :) ).

If I get it right, my idea of a "delayed (and manually started) sync of realtime logging"
all in all can't be accomplished, as I can not specify filters (e.g. exclude ...

Addendum:
I just realized that your so-called "Realtime Sync" is somewhat
similiar in what I described above.
(I didn't have a look at it as I took it literal by it's name:
Realtime Sync = Permanent Sync; i.e. kind of RAID etc.)

But what I actually mean is better described by something like ...

Enable FreeFilySync to keep track all file operations at sources.

Then, when it's synchronization time, it doesn't has to compare
the complete source with destination, but only perform the logged
operations on it's list.

Typically there will be only a small percentage of source data
that has to be ...

or even of size 0.

Is further sync processing stopped?
Or retry?
Or going one, but leaving tmp-files?
Etc.

FreeFileSync Forum

Search found 36 matches

Re: [REQUEST] Show resume (bytes added vs. deleted) after Compare run

[REQUEST] Show resume (bytes added vs. deleted) after Compare run

Re: [Bug] After Compare: Relative Path empty for Desktop and for bookmarkbackups

Re: [Bug] After Compare: Relative Path empty for Desktop and for bookmarkbackups

Re: [Bug] After Compare: Relative Path empty for Desktop and for bookmarkbackups

Re: [Bug] After Compare: Relative Path empty for Desktop and for bookmarkbackups

[Bug] After Compare: Relative Path empty for Desktop and for bookmarkbackups

Re: Mirror synchronizing into same destination

Re: Mirror synchronizing into same destination

Explanation for .run installation?

Re: Mirror synchronizing into same destination

Re: Mirror synchronizing into same destination

Mirror synchronizing into same destination

Re: What happens If fail-save copy fails?

Re: Synchronizing unique non-directory objects

Re: What happens If fail-save copy fails?

Re: Filter include/ exclude settings: Adding like source and destination

Re: [Feature Request] Filter: Consistency check

Re: Filter include/ exclude settings: Adding like source and destination

Re: Filter include/ exclude settings: Adding like source and destination

Re: Filter include/ exclude settings: Adding like source and destination

Re: [Feature Request] Filter: Consistency check

Re: Filter include/ exclude settings: Adding like source and destination

Re: Synchronizing unique non-directory objects

[Feature Request] Filter: Consistency check

Filter include/ exclude settings: Adding like source and destination

Journaling filesystems...

Synchronizing unique non-directory objects

Re: [Feature Request] Option if the replacing file is MUCH smaller than the to be replaced one

Re: What happens If fail-save copy fails?

Re: [Feature Request] Option if the replacing file is MUCH smaller than the to be replaced one

Re: [Feature Request] "A-priori mode"

Re: [Feature Request] "A-priori mode"

[Feature Request] "A-priori mode"

[Feature Request] Option if the replacing file is MUCH smaller than the to be replaced one

What happens If fail-save copy fails?