FreeFileSync Forum

There is a "Save" button in the top left of the window above the list of your saved configurations. It's greyed out until you change something in the configuration. You can also use Ctrl+S.

Sounds good.

Since rsync also does not preallocate by default, this should be fine. I just had a quick look at rsync's manpage and there is a switch that has to be turned on specifically.

--preallocate This tells the receiver to allocate each destination file to its eventual size before writing ...

I just installed and tested the 12.4 beta version and it works flawlessly now. Compression is applied correctly.

With the rise of btrfs (Fedora even ships it with zstd:1 compression enabled by default) it would be a neat feature for FFS to have an option to omit the fallocate step or generally omit ...

I also did a test with strace with a fresh btrfs subvolume to which I copied 5 files with 640 M.

strace freefilesync &> ~/ffstrace.txt

Result after the copy process with FFS:

sudo compsize /mnt/more
Processed 5 files, 5 regular extents (5 refs), 0 inline.
Type Perc Disk Usage Uncompressed ...

Thank you for the reply :)

I can confirm that both rsync -av as well as cp -v write the files in a compressed manner to my btrfs filesystem (or rather the kernel/btrfs itself does it right).

In the meanwhile I found out the "faulty" behaviour happens not only with FFS, but also with the program ...

Hello everyone! I am a big fan of FFS and use it almost everytime I have to copy or sync a large amount of data from one drive to another!

Today I noticed the following behaviour: When copying data to a btrfs partition with enabled compression (mount option compress-force=zstd:6) data copied with ...