-
Notifications
You must be signed in to change notification settings - Fork 19
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
Deactivate the read only parent after a scrub #1180
Conversation
If the scrub on a read only parent finishes without error, then send a deactivate to force a disconnect from all the downstairs.
I tested this on a bench gimlet which had a ROP parent for the boot disk. Here are some logs from propolis:
|
I did some digging through the deactivation state machine, and this seems reasonable. Once all three Downstairs are deactivated, the upstairs transitions back to It would probably be cleaner to not restart the client task immediately, but that's a larger refactoring, and this PR certainly doesn't make the situation worse. One question inspired by this PR: should |
The volume is still used by the rest of Propolis to send IOs, so I don't think we can take |
If the scrub on a read only parent finishes without error, then send a
deactivate to force a disconnect from all the downstairs.
This should fix #1090