From c4b31bdd5c93ee3184323a4d96bc252f92d9b0db Mon Sep 17 00:00:00 2001 From: Zygo Blaxell Date: Fri, 13 Dec 2024 22:44:38 -0500 Subject: [PATCH] extent scan: no need for "No ref for extent" debug message While a snapshot is being deleted, there will be a continuous stream of "No ref for extent" messages. This is a common event that does not need to be reported. There is an analogous situation when a call to open() fails with ENOENT. Signed-off-by: Zygo Blaxell --- src/bees-roots.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/bees-roots.cc b/src/bees-roots.cc index 19078c0..98e0434 100644 --- a/src/bees-roots.cc +++ b/src/bees-roots.cc @@ -645,7 +645,7 @@ BeesScanModeExtent::create_extent_map(const uint64_t bytenr, const ProgressTrack bedf.objectid(i.m_inum); const auto bti = bedf.at(i.m_offset); if (!bti) { - BEESLOGDEBUG("No ref for extent " << to_hex(bytenr) << " at root " << i.m_root << " ino " << i.m_inum << " offset " << to_hex(i.m_offset)); + // BEESLOGDEBUG("No ref for extent " << to_hex(bytenr) << " at root " << i.m_root << " ino " << i.m_inum << " offset " << to_hex(i.m_offset)); BEESCOUNT(extent_ref_missing); return; }