-
Notifications
You must be signed in to change notification settings - Fork 42
Incremental: do not call Manage_subdevs() from IncrementalRemove() #31
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
Incremental: do not call Manage_subdevs() from IncrementalRemove() #31
Conversation
83fc6b2 to
12989b5
Compare
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.
Hi,
Overall I agree with the change, I have a few minor questions or corrections.
Typo in commit desc ee89efa
dediated -> dedicated
Unnecessary dots in commit titles
456d4f0 to
2b121df
Compare
2b121df to
e25f104
Compare
c875c84 to
1c146da
Compare
Keep it documented in code. Signed-off-by: Mariusz Tkaczyk <[email protected]>
Add dedicated enum to reflect possible values for mentioned file. Not all values are mapped. Add map to present sysfs keywords. Signed-off-by: Mariusz Tkaczyk <[email protected]>
Incremental_remove() does not execute Manage_subdevs() now. Signed-off-by: Mariusz Tkaczyk <[email protected]>
In mdadm, we have more flexible apporach to typedefs. Signed-off-by: Mariusz Tkaczyk <[email protected]>
|
Nice change/cleanup. Do we have any tests in place to verify functionality change? |
|
I tested it functionally on my own with native and IMSM. No regression detected but it was minimal testing. You can see testing result here: |
|
@ncroxon, comparing to Nightly execution on the latest main. I see
|
This is a first part of HOT_REMOVE_DISK/SET_FAULTY rework. The goal is to not execute HOT_REMOVE_DISK ioctl on
mdadm --removepath with container.This PR changes following: