From ec780ac75f0177b12b0fd45378eb5cac40b0bfd0 Mon Sep 17 00:00:00 2001
From: David Zafman <dzafman@redhat.com>
Date: Mon, 28 Jan 2019 14:30:29 -0800
Subject: [PATCH] mon: A PG with PG_STATE_REPAIR doesn't mean damaged data,
 PG_STATE_INCONSISTENT does

Fixes: http://tracker.ceph.com/issues/38070

Signed-off-by: David Zafman <dzafman@redhat.com>
(cherry picked from commit a4b1574532ee4f789b30634f0eca03cc30ddcf8d)
---
 src/mon/PGMap.cc | 1 -
 1 file changed, 1 deletion(-)

diff --git a/src/mon/PGMap.cc b/src/mon/PGMap.cc
index c5def7d1ce6b..b1041b95feb9 100644
--- a/src/mon/PGMap.cc
+++ b/src/mon/PGMap.cc
@@ -2673,7 +2673,6 @@ void PGMap::get_health_checks(
     // Immediate reports
     { PG_STATE_INCONSISTENT,     {DAMAGED,     {}} },
     { PG_STATE_INCOMPLETE,       {UNAVAILABLE, {}} },
-    { PG_STATE_REPAIR,           {DAMAGED,     {}} },
     { PG_STATE_SNAPTRIM_ERROR,   {DAMAGED,     {}} },
     { PG_STATE_RECOVERY_UNFOUND, {DAMAGED,     {}} },
     { PG_STATE_BACKFILL_UNFOUND, {DAMAGED,     {}} },
-- 
2.47.3