Environment: 2 identical machines
Both running restic 0.15.2 compiled with go1.20.3 on linux/amd64
Both backing up to the same remote repo
I observe that on both machines, running ‘restic stats lastest --host A’ reports a size of 24.604 MiB.
The expected output should be something like 6 GiB.
Why do I have that expectation? Because the latest snapshot contains a file that is ~4 GiB which gets written just before the snapshot is created. This file (a tar file) seems to be correctly backed up: I restored it and checked md5sum: It’s the same for both the original and the restored file.
Things I noted
original file is read from ext4, restored file was saved to zfs
stat shows the same size for both files
md5sum is the same for both files
du on both files reports the same “apparent size”, but a different device usage (3,8GiB vs 1,8GiB - maybe because of the different FS?)
Nevermind the different size reported by “du”, restic should still not tell me the snapshot is “24 MiB”.
Do I have a wrong expectation, perhaps regarding the output of the stats command?
The default mode of stats should output the file size after a restore operation.
Can you provide the full output of restic stats latest --host A ? Please also check the output of restic ls --host A -l latest. How did you specify the snapshot for the restore command, also as latest --host A?
Update: It just happened again with the same 2 hosts backing up to a new repo. restic diff (latest, size is off vs. the previous one, where the size is normal) shows the files correctly (especially the large tar file being ‘replaced’ [old file -, new file +]). Size seems correct, too:
Added: 1.089 GiB
Removed: 1.031 GiB
Still, restic stats latest shows the snapshot size to be 28.435 MiB.