Control: tag -1 moreinfo
This doesn't look like a bug to me. Notice that the database is 5 GB
in size, and the indexes aren't even created yet. You just need more
diskspace. Try running duperemove on a subset of your files to see
how much space the DB needs for that and extrapolate from there.
You could also politely ask the developer on github whether he'd
consider adding a feature that more accurately computes the projected
diskspace; I cobbled together this awk program using the formula
mentioned in the manpage which should already be close after some
tweaking:
find /home -type f -printf '%s %p\n' \
| awk -M -e '{h+=$1;c+=length($0)-length($1)-1;};' \
-e 'END{printf "%i bytes\n", 90*(int(h/(128*1024))+1)+c}'
If you want to investigate this further, try to run the command again
like this (install package strace if you haven't already) and post the
last 30 or so lines:
strace -f duperemove -r -A -h --skip-zeroes \
--hashfile=/var/cache/duperemove-home-user /home/user/
Otherwise you should watch how the disk space situation develops while
duperemove is running:
while sleep 10; do df -h /var ; done | tee /tmp/df.log
Regards,
Dennis.
