From 007067b83fec5d4ff9e506754075c113b8324cfb Mon Sep 17 00:00:00 2001 From: Zygo Blaxell Date: Sat, 11 Dec 2021 14:12:32 -0500 Subject: [PATCH] docs: add missing 'adjust_offset_hit' counter Reported by York-Simon Johannsen via github issue 208. Signed-off-by: Zygo Blaxell --- docs/event-counters.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/event-counters.md b/docs/event-counters.md index 612010a..ab226d4 100644 --- a/docs/event-counters.md +++ b/docs/event-counters.md @@ -67,11 +67,12 @@ The `adjust` event group consists of operations related to translating stored vi * `adjust_exact`: A block address from the hash table corresponding to an uncompressed data block was processed to find its `(root, inode, offset)` references. * `adjust_exact_correct`: A block address corresponding to an uncompressed block was retrieved from the hash table and resolved to a physical block containing data that matches another block bees has already read. * `adjust_exact_wrong`: A block address corresponding to an uncompressed block was retrieved from the hash table and resolved to a physical block containing data that matches the hash but not the data from another block bees has already read (i.e. there was a hash collision). - * `adjust_hit`: A block address was retrieved from the hash table and resolved to a physical block containing data that matches the data from another block bees has already read (i.e. a duplicate match was found). + * `adjust_hit`: A block address was retrieved from the hash table and resolved to a physical block in an uncompressed extent containing data that matches the data from another block bees has already read (i.e. a duplicate match was found). * `adjust_miss`: A block address was retrieved from the hash table and resolved to a physical block containing a hash that does not match the hash from another block bees has already read (i.e. the hash table contained a stale entry and the data it referred to has since been overwritten in the filesystem). * `adjust_needle_too_long`: A block address was retrieved from the hash table, but when the corresponding extent item was retrieved, its offset or length were out of range to be a match (i.e. the hash table contained a stale entry and the data it referred to has since been overwritten in the filesystem). * `adjust_no_match`: A hash collision occurred (i.e. a block on disk was located with the same hash as the hash table entry but different data) . Effectively an alias for `hash_collision` as it is not possible to have one event without the other. * `adjust_offset_high`: The `LOGICAL_INO` ioctl gave an extent item that does not overlap with the desired block because the extent item ends before the desired block in the extent data. + * `adjust_offset_hit`: A block address was retrieved from the hash table and resolved to a physical block in a compressed extent containing data that matches the data from another block bees has already read (i.e. a duplicate match was found). * `adjust_offset_low`: The `LOGICAL_INO` ioctl gave an extent item that does not overlap with the desired block because the extent item begins after the desired block in the extent data. * `adjust_try`: A block address and extent item candidate were passed to `BeesResolver::adjust_offset` for processing.