-
Notifications
You must be signed in to change notification settings - Fork 306
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-16978 vos: fix issue in VOS pool recreation on faulty device rep… #15771
base: master
Are you sure you want to change the base?
Conversation
Ticket title is 'pool shard been deleted abnormally when daos service restart after doing nvme disk replace' |
src/include/daos_srv/bio.h
Outdated
@@ -1010,6 +1010,7 @@ int bio_copy(struct bio_io_context *ioctxt, struct umem_instance *umem, | |||
|
|||
enum bio_mc_flags { | |||
BIO_MC_FL_RDB = (1UL << 0), /* for RDB */ | |||
BIO_MC_RE_CRE = (1UL << 1), /* to identify recreate (e.g., in replace op) */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could rename it to BIO_MC_FL_RECREATE?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix done.
…lacing Add a flag to identify the recreate operation in vos pool creation, and pass it to bio/smd module to avoid setting the SMD_POOL_IN_CREATION flag for recreation case in nvme disk replacing operation. Run-GHA: true Signed-off-by: Jun Zeng <[email protected]>
…lacing
Add a flag to identify the recreate operation in vos pool creation, and pass it to bio/smd module to avoid setting the SMD_POOL_IN_CREATION flag for recreation case in nvme disk replacing operation.
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: