Skip to content

Ignore xfs dirty logs#144

Closed
27149chen wants to merge 1 commit intokubernetes:masterfrom
27149chen:ignore_xfs_dirty_logs
Closed

Ignore xfs dirty logs#144
27149chen wants to merge 1 commit intokubernetes:masterfrom
27149chen:ignore_xfs_dirty_logs

Conversation

@27149chen
Copy link

@27149chen 27149chen commented Mar 1, 2020

This PR try to fix the urgent issue #141 by ignoring the xfs dirty logs issue (do not replay dirty logs by default), and letting subsequent operations handle it.
But this is not a perfect solution, more discussion is in pr #132 .

ignore xfs dirty logs
260a5d9 
Signed-off-by: Lou <luogj@cn.ibm.com>
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Mar 1, 2020
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Mar 1, 2020

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: 27149chen
To complete the pull request process, please assign saad-ali
You can assign the PR to them by writing /assign @saad-ali in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@27149chen
Copy link
Author

27149chen commented Mar 1, 2020

/assign @gnufied

@27149chen
Copy link
Author

27149chen commented Mar 1, 2020

/assign @saad-ali

@27149chen
Copy link
Author

27149chen commented Mar 1, 2020

/cc @nktpro

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Mar 1, 2020

@27149chen: GitHub didn't allow me to request PR reviews from the following users: nktpro.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

/cc @nktpro

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@27149chen
Copy link
Author

27149chen commented Mar 6, 2020

@saad-ali , @gnufied please have a look.

@27149chen
Copy link
Author

27149chen commented Mar 6, 2020

/assign @ jsafrane

whymatter
whymatter reviewed Mar 19, 2020
View reviewed changes
mount/mount_linux.go
case xfsRepairErrorsDirtyLogs:
// mark the a dirty log issue as a warning, do you replay it by default.
klog.Warningf("A dirty log is detected on this xfs disk.")
return nil
Copy link

@whymatter whymatter Mar 19, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi I came across this pr because I do have exactly this problem using ceph rbd with xfs and rook.io
Wouldn't this cause the same potential "compounding of problems" as in #132 ?

Copy link
Author

@27149chen 27149chen Mar 23, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, I will. But 132 is still under discussion.

@27149chen
Copy link
Author

27149chen commented Mar 23, 2020

/assign @dims

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Mar 25, 2020

@27149chen: PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 25, 2020
@astraldawn astraldawn mentioned this pull request Apr 2, 2020
Closed
9 tasks
@dims dims removed their assignment Apr 29, 2020
@fejta-bot
Copy link

fejta-bot commented Jul 28, 2020

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 28, 2020
@fejta-bot
Copy link

fejta-bot commented Aug 27, 2020

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 27, 2020
@fejta-bot
Copy link

fejta-bot commented Sep 26, 2020

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Sep 26, 2020

@fejta-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@andyzhangx andyzhangx Awaiting requested review from andyzhangx

@saad-ali saad-ali Awaiting requested review from saad-ali

1 more reviewer

@whymatter whymatter whymatter left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

@gnufied gnufied

@saad-ali saad-ali

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

7 participants

@27149chen @k8s-ci-robot @fejta-bot @whymatter @gnufied @dims @saad-ali