Delete before overwrite if no free space

[glacialman]

Hi, FFS is very useful and efficient, thank you. In the case of Mirror (probably also in others), I found a problem, I do a striking example:
- I have a source folder "A" that contains some files
- I execute the Mirror to obtain a perfect copy of the source folder "A" in a USB destination drive that already contains "A" folder (and old file versions) and the destination drive doesn't have free space (or it's very small)
The actual result is that some old files cannot be overwritten because are biggest than the free space. In my opinion, before indicate that the free space is insufficient (ignore or retry is useless), for each file, would be useful calculate if is sufficient for needs: the free destination space + the dimension of the old file; in positive case, probably will necessary to delete old file before writing the new file. Excuse me for my language, I do not know english language very well. Thanks for your time, bye.

[Zenju]

You can disable "fail-safe copy" in global settings which will avoid creating a temporary file, thus reduce the peak space consumption during sync. However I would not recommend this in general, since "fail-safe copy" is a protection against data corruption in case of unexpected interruptions like power loss or network drops.

[glacialman]

You can disable "fail-safe copy" in global settings which will avoid creating a temporary file, thus reduce the peak space consumption during sync. However I would not recommend this in general, since "fail-safe copy" is a protection against data corruption in case of unexpected interruptions like power loss or network drops.

Hi, thank you for all. In this moment the option "fail-safe copy" seems not to operate. In both cases (flagged or unflagged), when I start the synchronization, the space available on the destination unit is calculated and, as there is insufficient space, is displayed the warning message. By analyzing the information I noticed that is calculated the space available but not the space that will be available after synchronization (sum of the space available and of the dimensions of the files to delete). If this procedure exists for security needs (the files to be deleted are removed only before copying the newest), only in this case (insufficient space), a solution could be to automatically postpone copying of larger files. Thank you, bye.