The crawl_extent_dup duplicate-queue drop and the block_map_fetch
temp-file ref skip are diagnostic events: bees handles both cases
itself and operators do not need to take action, as they might with
a warning. Log them at debug level instead of warn.
Assisted-by: Claude-Code:claude-fable-5
// Skipping is the safe action -- the data is not ours to
// hash -- but it is not a normal outcome.
BEESCOUNT(block_map_ref_tempfile);
- BEESLOGWARN("block_map_fetch: ref into temp file root "
+ BEESLOGDEBUG("block_map_fetch: ref into temp file root "
<< ref.root() << " inum " << ref.inum()
<< " offset " << to_hex(ref.offset())
<< " on extent " << to_hex(node.m_bytenr)
// extent lives at this address, not one extent queued
// twice from one view.
BEESCOUNT(crawl_extent_dup);
- BEESLOGWARN("crawl_extent_dup: extent already queued for scanning\n"
+ BEESLOGDEBUG("crawl_extent_dup: extent already queued for scanning\n"
<< "\tin flight: " << held_inflight << "\n"
<< "\tdropped: " << this_inflight);
continue;