New answers tagged ext4
For many reasons. For example, you don't use -a or -l, so the symbolic links are converted to normal files. You don't use -H so hard links become normal files. And there is also a phenomenon on Unix/Linux, that a removed file still consumes the space until all the processes that had it opened decide to close it. Might there be open files on Destination ...
Some help from Iain identified that the mounted networked attached storage had gone away. All the backups were being written to the /rootfs filling it very quickly. I'll just need to figure out why that happened and ensure that it doesn't happen again.
Are the block sizes used on both filesystems the same ? If you have real doubts about files having gotten corrupted, consider using the (slow!) -c option to rsync.
The most likely cause is hard links. Rsync by default turns 2 hardlinked files into duplicate files on the target taking up twice the disk space. If you want to preserve hard links add the -H/--hard-links option. The next most likely issue is sparse files. Rsync by default does not write any files as sparse files even if they are on the source (it can't ...
The rsync FAQ page lists these reasons: https://sanitarium.net/rsyncfaq/#differentsizes However the only way to know is to compare the files. For a small number of files you could do diff -r /mnt/data /mnt/data-BACKUP. However if that stops mid-way, it can't be restarted from where it left off. Older diff programs don't handle binary files well. For a ...
Might I suggest using an SQL database instead? This would likely transform this perceived weakness in your application into a strength.
NFS protocol does not support extended attributes and. as a result, you can't transfer local extended attributes to the server. There are some effort in NFS community to make it possible, but it will take some time until it will be available.
Top 50 recent answers are included