-
Notifications
You must be signed in to change notification settings - Fork 304
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-16291 bio: auto detect faulty for an unplugged device #14850
Merged
Conversation
This file contains 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
Ticket title is 'DAOS engine doesn't handle hot-removal of healthy NVMe disk' |
tanabarr
previously approved these changes
Jul 31, 2024
wangshilong
previously approved these changes
Aug 1, 2024
Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-14850/1/execution/node/1543/log |
liuxuezhao
previously approved these changes
Aug 1, 2024
When a health device is unplugged, we should keep counting the I/O errors against the device, once the number of I/O errors reached faulty criteria, the unplugged device should be automatically marked as FAULTY and trigger targets exclusion accordingly. Required-githooks: true Signed-off-by: Niu Yawei <[email protected]>
NiuYawei
dismissed stale reviews from liuxuezhao, wangshilong, and tanabarr
via
August 12, 2024 08:59
3b04848
NiuYawei
force-pushed
the
niu/DAOS-16291
branch
from
August 12, 2024 08:59
c86ceaf
to
3b04848
Compare
wangshilong
approved these changes
Aug 13, 2024
liuxuezhao
approved these changes
Aug 15, 2024
tanabarr
approved these changes
Aug 15, 2024
NiuYawei
added a commit
that referenced
this pull request
Aug 15, 2024
When a health device is unplugged, we should keep counting the I/O errors against the device, once the number of I/O errors reached faulty criteria, the unplugged device should be automatically marked as FAULTY and trigger targets exclusion accordingly. Signed-off-by: Niu Yawei <[email protected]>
gnailzenh
pushed a commit
that referenced
this pull request
Aug 20, 2024
…14936) When a health device is unplugged, we should keep counting the I/O errors against the device, once the number of I/O errors reached faulty criteria, the unplugged device should be automatically marked as FAULTY and trigger targets exclusion accordingly. Signed-off-by: Niu Yawei <[email protected]>
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.
When a health device is unplugged, we should keep counting the I/O errors against the device, once the number of I/O errors reached faulty criteria, the unplugged device should be automatically marked as FAULTY and trigger targets exclusion accordingly.
Required-githooks: true
Before requesting gatekeeper:
Features:
(orTest-tag*
) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.Gatekeeper: