From 1f9f14e3f60b5eaa2cf19ab7754b58af60063584 Mon Sep 17 00:00:00 2001 From: Samuel Just Date: Tue, 15 Apr 2025 12:46:21 -0700 Subject: [PATCH] crimson/osd/recovery_backend: do not resolve_clone in scan_for_backfill We're looking for the exact hobject_t specified. Fixes: https://tracker.ceph.com/issues/70935 Signed-off-by: Samuel Just --- src/crimson/osd/recovery_backend.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/crimson/osd/recovery_backend.cc b/src/crimson/osd/recovery_backend.cc index b0dbcfba9839f..dc9659972410e 100644 --- a/src/crimson/osd/recovery_backend.cc +++ b/src/crimson/osd/recovery_backend.cc @@ -235,8 +235,8 @@ RecoveryBackend::scan_for_backfill( co_await interruptor::parallel_for_each(objects, seastar::coroutine::lambda([FNAME, this, version_map] (const hobject_t& object) -> interruptible_future<> { DEBUGDPP("querying obj:{}", pg, object); - auto obc_manager = pg.obc_loader.get_obc_manager(object); - co_await pg.obc_loader.load_and_lock( + auto obc_manager = pg.obc_loader.get_obc_manager( + object, /* resolve_clone = */ false); obc_manager, RWState::RWREAD ).handle_error_interruptible( crimson::ct_error::assert_all("unexpected error") -- 2.39.5