noload option appended#7
Open
EnvyusKennys wants to merge 22 commits into
Open
Conversation
Author
houz42
reviewed
Mar 11, 2022
houz42
requested changes
Mar 14, 2022
added 8 commits
March 14, 2022 17:31
houz42
requested changes
Apr 19, 2022
Member
|
可以合并了吧 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe what this PR does
Adding noload option for readonly mount condition to avoid journal replay
Provide any external context for the change, if any.
From log:
Warning FailedMount 20m kubelet MountVolume.MountDevice failed for volume "pvc-5841825d-31fc-49af-b7f6-dfaefadc7daf" : rpc error: code = Internal desc = 'fsck' found errors on device /dev/rbd1 but could not correct them: fsck from util-linux 2.32.1
/dev/rbd1: Superblock needs_recovery flag is clear, but journal has data.
/dev/rbd1: Run journal anyway
/dev/rbd1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Related issues
Future concerns
May need further testing in prd environments