[DragonFlyBSD - Bug #2759] (Resolved) hammer(8) doesn't respect the timelimit for deduplication

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Fri Jan 9 02:49:03 PST 2015

Issue #2759 has been updated by ftigeot.

Status changed from Feedback to Resolved
% Done changed from 90 to 100

Fix pushed to -master as 3a92efe3ce8f11b83b469609135c5fedaafa6632 .

Bug #2759: hammer(8) doesn't respect the timelimit for deduplication

* Author: ftigeot
* Status: Resolved
* Priority: High
* Assignee: tuxillo
* Category: Userland
* Target version: 4.2.x
- a storage server with a 20TB /data volume
- a dataset potentially deduplication-friendly (protein sequences)
- deduplication has been enabled with a 5mn per day timelimit for /data

- hammer(8) is running most of the day, inducing a high background I/O load on the disks
- the particular command is "hammer -t 300 dedup"

That command is run from the nightly hammer cleanup cron. It starts at 3am an never finishes.

A quick test on a brand new hammer volume confirms the -t argument to hammer dedup has no effect.
hammer dedup will run forever as long as there is still data to deduplicate.

cmd_dedup01.diff (3.86 KB)

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

More information about the Bugs mailing list