Since upgrading from Ubuntu 10.04 to 12.04 I noticed restore has been suggesting it cannot restore all the files intended to be captured by dump.
I am seeing output from restore along the lines of
restore: ./tigi/.cache/dconf/user: ftruncate: Invalid argument
I took the dump using an LVM2 snapshot and restored against the same snapshot 3 minutes later.
uname -a:
Linux yoda 3.2.0-25-generic-pae #40-Ubuntu SMP Wed May 23 22:11:24 UTC 2012 i686 i686 i386 GNU/Linux
Trace file of commands run and output
28/6/2012 rumex: I restored to /mnt/restoredFs and performed a diff -r /snapshop /mnt/restoredFs. The diff found no differences. I would cautiously assume that this error message is potentially only annoying.
It's not completely obvious to me whether this was restore -C testing or not but the error of calling ftruncate on a non-file when testing with restore -C was fixed in 2016.
Closed assuming this is a long fixed restore -C bug. I have not encounted this problem during the 0.4b48 testing at all.