Bug 2092529

Summary: [GSS] fsck error `/dev/rbd0: Inode has an invalid extent node ` is observed
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Sonal <sarora>
Component: cephAssignee: Ilya Dryomov <idryomov>
ceph sub component: RBD QA Contact: Neha Berry <nberry>
Status: CLOSED NOTABUG Docs Contact:
Severity: medium    
Priority: unspecified CC: abhishku, bniver, hnallurv, idryomov, madam, muagarwa, ocs-bugs, odf-bz-bot, pnataraj, sostapov, vshankar
Version: 4.9   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-10-19 06:32:56 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:

Description Sonal 2022-06-01 18:33:15 UTC 
Description of problem (please be detailed as possible and provide log
snippests):

fsck error is observed on noobaa-db pod:

/dev/rbd0 contains a file system with errors, check forced.
/dev/rbd0: Inode 1310756 has an invalid extent node (blk 5275725, lblk 0)


Version of all relevant components (if applicable):
ODF 4.9.6

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


Is there any workaround available to the best of your knowledge?
No

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

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:
-

Actual results:
noobaa-db pod is in pending state

Expected results:
It should be in running state

Additional info:
In next private comment
Comment 4 Scott Ostapovicz 2022-06-06 12:39:40 UTC 
@vshankar Please take a look.
Comment 5 Venky Shankar 2022-06-06 13:27:49 UTC 
(In reply to Scott Ostapovicz from comment #4)
> @vshankar Please take a look.

RBD related.