Duperemove continuing infinitely after getting stuck on a file

I've encountered an issue where duperemove will run into "invalid argument" on a certain file and just continue running and using a bunch of cpu+battery life forever unless I turn it off. I left it for about an hour yesterday with

watch -n 0.5 systemctl status btrfs-dedup@var-home.service

watch -n 0.5 systemctl status btrfs-dedup@var-home.service

watch -n 0.5 systemctl status btrfs-dedup@var-home.service

watch -n 0.5 systemctl status btrfs-dedup@var-home.service and it never moved past the files it was stuck on. When I restart the service it'll scan a few files then run into the problem again.

https://paste.centos.org/view/58666fce

wolfyreload•5/29/24, 7:40 PM

https://github.com/markfasheh/duperemove/issues/199 Looks like there is a known duperemove issue that sometimes occurs when the tool is run by an unprivileged user.

GitHub

"Invalid argument" when trying to deduplicate as non-root; prevents...

I have installed the current master (commit 1dbf731) on Linux Mint 18, Kernel: $ uname -rv 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 I have an empty btrfs volume mounted on /mn...

DaphOP•5/29/24, 9:15 PM

Thanks. That's interesting as it occurred when run as a systemd service

DaphOP•5/29/24, 9:15 PM

which I think is as root

DaphOP•5/29/24, 10:03 PM

Update on this, it's moved on to another file but taking just as long with this next one, except with the status: had status (1) "data changed".had status (1) "data changed".

wolfyreload•5/30/24, 5:11 AM

It's probably just taking a really long time hashing the files, esp if the file is 4+GB in size

Duperemove continuing infinitely after getting stuck on a file

Similar Threads

Similar Threads

Similar Threads