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

expunge sled: planner must not use physical disks being removed #5372

Closed
4 tasks done
Tracked by #5149
smklein opened this issue Apr 1, 2024 · 1 comment
Closed
4 tasks done
Tracked by #5149

expunge sled: planner must not use physical disks being removed #5372

smklein opened this issue Apr 1, 2024 · 1 comment
Assignees
Milestone

Comments

@smklein
Copy link
Collaborator

smklein commented Apr 1, 2024

This is probably blocked on #3526, which I believe is adding physical disk policies described in RFD 457. Once we have this, the blueprint planner will need to make sure that:

@smklein smklein self-assigned this Apr 1, 2024
@smklein smklein added this to the 9 milestone Apr 23, 2024
smklein added a commit that referenced this issue Apr 23, 2024
…5601)

Previously, the planner placed Crucible zones on zpools unconditionally.
Now, we respect the policy and state of disks to
limit which disks are targets to receive these zones.

Partial fix of #5372
smklein added a commit that referenced this issue May 30, 2024
Expunges zones for which the corresponding physical disk, holding
durable data, has been removed.

A follow-up PR will be necessary to expunge zones which have had their
transient zone filesystems removed,
but Nexus is not yet aware of where zone placement decisions are made.

Partial fix of #5372
@smklein
Copy link
Collaborator Author

smklein commented Jul 11, 2024

There are more details with actually plumbing the expungement command through (#5994), but from the planner perspective, this is complete

@smklein smklein closed this as completed Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant