Bug 1595283 - [Backport] osd: eternal stuck PG in 'unfound_recovery' http://tracker.ceph.com/issues/24373
Summary: [Backport] osd: eternal stuck PG in 'unfound_recovery' http://tracker.ceph.co...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 2.5
Hardware: x86_64
OS: Linux
high
high
Target Milestone: z2
: 2.5
Assignee: Josh Durgin
QA Contact: Vasishta
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-26 13:34 UTC by Mike Hackett
Modified: 2021-12-10 16:28 UTC (History)
10 users (show)

Fixed In Version: RHEL: ceph-10.2.10-37.el7cp Ubuntu: ceph_10.2.10-32redhat1
Doc Type: Bug Fix
Doc Text:
Under some circumstances placement groups (PGs) could become stuck in the "recovery_unfound" state when a copy of the data was available after an OSD was marked down and then up. To fix this issue, OSDs reset peering when they are marked down and then up, and PGs no longer get stuck in the "recovery_unfound" state.
Clone Of:
Environment:
Last Closed: 2018-09-05 19:39:32 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2651 0 None None None 2018-09-05 19:40:25 UTC

Description Mike Hackett 2018-06-26 13:34:07 UTC 
Description of problem:\
Request to back port http://tracker.ceph.com/issues/24373 to Jewel (RHCS 2.5).

Version-Release number of selected component (if applicable):
2.5

PR: https://github.com/ceph/ceph/pull/22456
Comment 14 Vasishta 2018-08-30 07:43:32 UTC 
Hi,

Followed steps mentioned in description of http://tracker.ceph.com/issues/24373

Observed that PGs weren't stuck in unfound_recovery and working fine. Moving to VERIFIED state.

Regards,
Vasishta shastry
QE, Ceph
Comment 16 errata-xmlrpc 2018-09-05 19:39:32 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:2651
Note You need to log in before you can comment on or make changes to this bug.