Project

General

Profile

Bug #24876

snaptrim_error state cannot be cleared without a new snaptrim

Added by Greg Farnum over 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Snapshots
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
OSD
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

A user on the list reported they had PGs in state "active+clean+snaptrim_error". Investigating, I found that the only way you can get the snaptrim_error state is if the call to pg->trim_object() from PrimaryLogPG::AwaitAsyncWork::react(const DoSnapWork&) returns an error. And that state doesn't get cleared by scrubbing; only in the functions PrimaryLogPG::AwaitAsyncWork::AwaitAsyncWork() and when it exits the WaitReservation state with a SnapTrimReserved transition.

Also available in: Atom PDF