I am using 3.19.3 kernel, v3.19-rc2 btrfs-progs and v0.09-1 duperemove.
I have a btrfs lzo-compressed /home volume and I ran
duperemove -rdhv /home
It took over a day (no problem for me, it was a quiet time and it's a vm
on so-so underlying hardware), and it reported lots of matched extents.
Just the last few lines (file names removed) were:
Dedupe 59 extents with target: (0.0, 208.0M), "/home/..."
...
Dedupe 1 extents with target: (0.0, 224.8M), "/home/..."
...
Dedupe 1 extents with target: (0.0, 225.4M), "/home/..."
...
Dedupe 1 extents with target: (0.0, 1.5G), "/home/..."
Kernel processed data (excludes target files): 43.0G
Comparison of extent info shows a net change in shared extents of: 128.0K
From `btrfs fi usage` before/after reporting of estimated free space I
think I gained about 1G space (not 128K). But even this is a minimal
gain compared with the reported 43G (which relates much more closely IMO
to the actual shared extents found by duperemove). Why is the actual
space gain (128K? 1G?) so small compared to the total of shared extents
(43G maybe)?
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
