]> git.hungrycats.org Git - bees/commitdiff
extent scan: no need for "No ref for extent" debug message
authorZygo Blaxell <bees@furryterror.org>
Sat, 14 Dec 2024 03:44:38 +0000 (22:44 -0500)
committerZygo Blaxell <bees@furryterror.org>
Sat, 14 Dec 2024 20:02:39 +0000 (15:02 -0500)
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 <bees@furryterror.org>
src/bees-roots.cc

index 19078c04ffb335fd895eb1e239bdb31d244a8a63..98e0434891eb5d3569a5c33f8f2944987ad04b20 100644 (file)
@@ -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;
                        }