Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DAOS-15041 bio: handle normal device hot remove #13635

Merged
merged 2 commits into from
Jan 26, 2024
Merged

Conversation

NiuYawei
Copy link
Contributor

When a normal device is hot removed before being marked as faulty, the faulty reaction won't be performed, so that we need to close opened blobs when teardown the device, at the same time, the closed blobs need be opened on setup when the normal device is plugged back (in which case reint won't be triggered).

Before requesting gatekeeper:

  • Two review approvals and any prior change requests have been resolved.
  • Testing is complete and all tests passed or there is a reason documented in the PR why it should be force landed and forced-landing tag is set.
  • Features: (or Test-tag*) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.
  • Commit messages follows the guidelines outlined here.
  • Any tests skipped by the ticket being addressed have been run and passed in the PR.

Gatekeeper:

  • You are the appropriate gatekeeper to be landing the patch.
  • The PR has 2 reviews by people familiar with the code, including appropriate watchers.
  • Githooks were used. If not, request that user install them and check copyright dates.
  • Checkpatch issues are resolved. Pay particular attention to ones that will show up on future PRs.
  • All builds have passed. Check non-required builds for any new compiler warnings.
  • Sufficient testing is done. Check feature pragmas and test tags and that tests skipped for the ticket are run and now pass with the changes.
  • If applicable, the PR has addressed any potential version compatibility issues.
  • Check the target branch. If it is master branch, should the PR go to a feature branch? If it is a release branch, does it have merge approval in the JIRA ticket.
  • Extra checks if forced landing is requested
    • Review comments are sufficiently resolved, particularly by prior reviewers that requested changes.
    • No new NLT or valgrind warnings. Check the classic view.
    • Quick-build or Quick-functional is not used.
  • Fix the commit message upon landing. Check the standard here. Edit it to create a single commit. If necessary, ask submitter for a new summary.

When a normal device is hot removed before being marked as faulty,
the faulty reaction won't be performed, so that we need to close
opened blobs when teardown the device, at the same time, the closed
blobs need be opened on setup when the normal device is plugged
back (in which case reint won't be triggered).

Signed-off-by: Niu Yawei <[email protected]>
Copy link

github-actions bot commented Jan 19, 2024

Bug-tracker data:
Ticket title is 'handle unplugging normal device'
Status is 'In Review'
https://daosio.atlassian.net/browse/DAOS-15041

Copy link
Contributor

@tanabarr tanabarr left a comment

Choose a reason for hiding this comment

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

LGTM but the area code is not familiar to me so I won't approve

@daosbuild1
Copy link
Collaborator

Test stage Functional Hardware Medium completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-13635/1/testReport/

}

if (closed_blobs) {
D_DEBUG(DB_MGMT, "blobstore:%p has %d closed blobs\n",
Copy link
Contributor

Choose a reason for hiding this comment

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

maybe a assertion D_ASSERT(bxb->bxb_ready == true).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

why? the bxb_ready should be false in this case.

bio_blob_close(ioc, true);
}

if (opened_blobs) {
Copy link
Contributor

Choose a reason for hiding this comment

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

[Question]when we will free io_channel?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

When all opened blobs are closed, it could move on to putting io channel (see following code).

@NiuYawei NiuYawei requested a review from a team January 26, 2024 06:23
@NiuYawei NiuYawei merged commit 5f1bd41 into master Jan 26, 2024
47 of 48 checks passed
@NiuYawei NiuYawei deleted the niu/DAOS-15041 branch January 26, 2024 06:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

6 participants