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