Bug 2056818
Summary: | [GSS][RADOS][RGW] Scrub errors (omap_digest_mismatch) on PGs of RGW metadata pools after upgrade to RHCS 5 | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Karun Josy <kjosy> |
Component: | RADOS | Assignee: | Neha Ojha <nojha> |
Status: | CLOSED ERRATA | QA Contact: | Tintu Mathew <tmathew> |
Severity: | high | Docs Contact: | Mary Frances Hull <mhull> |
Priority: | unspecified | ||
Version: | 5.0 | CC: | akupczyk, amathuri, assingh, bhubbard, ceph-eng-bugs, ceph-qe-bugs, choffman, gjose, gsitlani, ksirivad, lflores, lithomas, mhackett, mhull, mmuench, ngangadh, nojha, nravinas, pdhange, rfriedma, rmandyam, rzarzyns, sseshasa, tmathew, tpetr, tserlin, vumrao |
Target Milestone: | --- | ||
Target Release: | 5.1z1 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | ceph-16.2.7-103.el8cp | Doc Type: | Bug Fix |
Doc Text: |
.Replicated pools do not result in inconsistent placement groups (PGs)
Before this update, partial recovery did not set `clean_omap` to `false` for `CEPH_OSD_OP_OMAPRMKEYRANGE` operations. This caused replicated pools with inconsistent PGs due to incomplete omap recovery.
With this release, marking `omap` as `dirty` for all omap writer operations, including `CEPH_OSD_OP_OMAPRMKEYRANGE`, results in no inconsistent PGs due to incomplete recovery.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-05-18 10:38:15 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: | 2085458 |
Comment 61
Neha Ojha
2022-05-17 19:46:11 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 (Red Hat Ceph Storage 5.1 Bug Fix update), 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-2022:4622 |