Skip to content

Conversation

@hawkw
Copy link
Member

@hawkw hawkw commented Jan 29, 2026

Propolis should not launch scrubs when constructing a Crucible backend for a read-only disk. Because the Crucible volume itself is read-only, the scrub will never succeed, so we shouldn't waste time attempting it.

This commit changes the CrucibleBackend to skip launching scrubs if the backend is readonly.

Propolis should not launch scrubs when constructing a Crucible backend
for a read-only disk. Because the Crucible volume itself is read-only,
the scrub will never succeed, so we shouldn't waste time attempting it.

This commit changes the `CrucibleBackend` to skip launching scrubs if
the backend is readonly.
@hawkw hawkw requested review from jmpesp and leftwo January 29, 2026 21:26
//
// We should not scrub read-only volumes, as we cannot write back to
// them, due to...you know, being read-only. So just don't do that.
if !opts.is_read_only() && volume.has_read_only_parent() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not convinced Nexus can construct a read only volume with a read_only_parent, but I suppose nothing stops you from sending propolis a toml directly that contains such a beast. So, it's probably best to just prevent it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmpesp told me it was possible, though I'm not sure if it will currently happen for the way we construct ro disks or not?

@hawkw hawkw merged commit 191305e into master Jan 30, 2026
12 checks passed
@hawkw hawkw deleted the eliza/i-dont-want-no-scrubs branch January 30, 2026 22:48
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

Successfully merging this pull request may close these issues.

4 participants