Project

General

Profile

Actions
Copy link

Bug #24652

closed

OSD crashes when repairing pg

Added by Ana Aviles almost 6 years ago. Updated almost 6 years ago.

Status:
Won't Fix
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

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

Description

After a deep-scrub on the primary OSD for the pg we get:

2018-06-25 14:13:39.261196 7fbc0c821700  0 log_channel(cluster) log [INF] : 0.20 deep-scrub starts
2018-06-25 14:14:11.362752 7fbc0c821700 -1 log_channel(cluster) log [ERR] : 0.20 shard 31 missing d5bd3420/rbd_data.15cec2ae8944a.00000000000dfbd4/head//0
2018-06-25 14:14:11.362759 7fbc0c821700 -1 log_channel(cluster) log [ERR] : 0.20 shard 35 missing d5bd3420/rbd_data.15cec2ae8944a.00000000000dfbd4/head//0
2018-06-25 14:15:27.416461 7fbc0c821700 -1 log_channel(cluster) log [ERR] : 0.20 deep-scrub 1 missing, 0 inconsistent objects
2018-06-25 14:15:27.416478 7fbc0c821700 -1 log_channel(cluster) log [ERR] : 0.20 deep-scrub 2 errors

After issuing a pg repair the pg is seemingly repaired (HEALTH_OK) but the primary OSD crashes right after fixing the pg. The crashed OSD restarts automatically without problems. However when manually issuing a deep-scrub on the pg we get back to the initial inconsistent pg

OSD logs (debug osd = 20)
OSD.35 primary b1a76fc3-ebd3-4061-a6c3-7d75ffc51471
OSD.31 secondary f8134aef-f141-4241-b0f0-a60b2630e446
OSD.44 secondary 53272d75-014b-40af-a064-36c043d8cd57

Actions
Copy link

Also available in: Atom PDF