From 88c7eb801006525db54f3c99f1195908e31f0d74 Mon Sep 17 00:00:00 2001 From: Stefan Boberg Date: Sat, 14 Mar 2026 23:00:59 +0100 Subject: Reset m_LastGcExpireTime when gc_state timestamps are bogus When the stored gc_state has mismatched clock resolution, m_LastGcExpireTime suffers the same issue as m_LastGcTime. Reset it back to TimePoint::min() so the disk usage log replay does not incorrectly filter out entries. --- src/zenstore/gc.cpp | 1 + 1 file changed, 1 insertion(+) (limited to 'src/zenstore') diff --git a/src/zenstore/gc.cpp b/src/zenstore/gc.cpp index f4bb80b69..f3edf804d 100644 --- a/src/zenstore/gc.cpp +++ b/src/zenstore/gc.cpp @@ -1782,6 +1782,7 @@ GcScheduler::Initialize(const GcSchedulerConfig& Config) // between the build that wrote gc_state and this build) or too far in the past. m_LastGcTime = GcClock::Now(); m_LastLightweightGcTime = m_LastGcTime; + m_LastGcExpireTime = GcClock::TimePoint::min(); } m_AttachmentPassIndex = SchedulerState["AttachmentPassIndex"sv].AsUInt8(); } -- cgit v1.2.3