Bug 2120944 - Large Omap objects found in pool 'ocs-storagecluster-cephfilesystem-metadata'
Summary: Large Omap objects found in pool 'ocs-storagecluster-cephfilesystem-metadata'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: ceph
Version: 4.8
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ODF 4.13.0
Assignee: Venky Shankar
QA Contact: Vishakha Kathole
URL:
Whiteboard:
: 2165608 (view as bug list)
Depends On:
Blocks: 2155275 2159294 2164338
TreeView+ depends on / blocked
 
Reported: 2022-08-24 05:32 UTC by Manjunatha
Modified: 2023-08-09 16:37 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2159294 (view as bug list)
Environment:
Last Closed: 2023-06-21 15:22:18 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 55215 0 None None None 2022-11-17 09:20:58 UTC
Ceph Project Bug Tracker 57481 0 None None None 2022-09-08 20:50:11 UTC
Red Hat Product Errata RHBA-2023:3742 0 None None None 2023-06-21 15:23:47 UTC

Comment 2 Scott Ostapovicz 2022-08-31 14:50:56 UTC 
So there is no effect here other than the health status being set to HEALTH_WARN?  In any case, assigning this to Josh for further disposition.
Comment 4 Josh Durgin 2022-09-07 20:29:40 UTC 
Greg, is there any known issue with this kind of metadata object being this large?
Comment 42 Venky Shankar 2023-02-22 02:38:38 UTC 
*** Bug 2165608 has been marked as a duplicate of this bug. ***
Comment 62 errata-xmlrpc 2023-06-21 15:22:18 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 OpenShift Data Foundation 4.13.0 enhancement and 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-2023:3742
Note You need to log in before you can comment on or make changes to this bug.