Bug 1508935
Summary: | osd/ReplicatedPG.cc: recover_replicas: object added to missing set for backfill, but is not in recovering, error! | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Vikhyat Umrao <vumrao> |
Component: | RADOS | Assignee: | David Zafman <dzafman> |
Status: | CLOSED ERRATA | QA Contact: | Parikshith <pbyregow> |
Severity: | high | Docs Contact: | Aron Gunn <agunn> |
Priority: | high | ||
Version: | 2.3 | CC: | agunn, anharris, bschmaus, ceph-eng-bugs, dzafman, hnallurv, jdurgin, kchai, kdreyer, linuxkidd, tserlin |
Target Milestone: | rc | ||
Target Release: | 2.5 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RHEL: ceph-10.2.10-1.el7cp Ubuntu: ceph_10.2.10-2redhat1xenial | Doc Type: | Bug Fix |
Doc Text: |
.Unreconstructable object errors are not handled properly
During a backfill or recovery operation of an erasure coded pool, the unreconstructable object errors were not handled properly. As a consequence, the OSDs terminated unexpectedly with the following message:
----
osd/ReplicatedPG.cc: recover_replicas: object added to missing set for backfill, but is not in recovering, error!
----
With this update, the error handling has been corrected and two new placement group (PG) states have been added: `recover_unfound` and `backfill_unfound`. As a result, the OSD does not terminate unexpectedly, and the PG state indicates that the PG contains unfound objects.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-21 19:44:55 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1536401 |
Description
Vikhyat Umrao
2017-11-02 14:17:13 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:0340 |