Bug 2048998 - [GSS]fsck errors on noobaa-db pvc
Summary: [GSS]fsck errors on noobaa-db pvc
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: ceph
Version: 4.8
Hardware: s390x
OS: Linux
urgent
high
Target Milestone: ---
: ---
Assignee: Ilya Dryomov
QA Contact: Harish NV Rao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-01 10:09 UTC by Sonal
Modified: 2023-08-09 16:37 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-19 07:35:53 UTC
Embargoed:


Attachments (Terms of Use)

Description Sonal 2022-02-01 10:09:02 UTC
Description of problem (please be detailed as possible and provide log
snippests):

Noobaa-db is in Pending state. Found fsck error for the rbd device:

Internal desc = 'fsck' found errors on device /dev/rbd0 but could not correct them: fsck from util-linux 2.32.1


Version of all relevant components (if applicable):
OCS 4.8

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, unable to use MCG

Is there any workaround available to the best of your knowledge?
Run fsck to repair fs

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2

Can this issue reproducible?
in customer's environment

Can this issue reproduce from the UI?
No

If this is a regression, please provide more details to justify this:
No


Actual results:
noobaa-db pvc fails to mount

Expected results:
Noobaa-db pod should be in running state

Additional info:
In next private comment

Comment 15 Scott Ostapovicz 2022-02-03 14:16:29 UTC
Ilya, I guess the outstanding question is how do they repair the volume that has been corrupted.


Note You need to log in before you can comment on or make changes to this bug.