You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is primary for the use cases where we expressly have thin-provisioning managed on enterprise SAN storage.
Thin-on-thin is generally not a desirable solution for various reasons, but complicates storage reporting when both are active.
I would request the option to have a storage pool designated as either thick or thin provisioned, though I can understand the issues that might arise with snapshots.
And even though disabling overprivisioning solves some issues, I'd rather have the option of thin-provisioning being completely delegated to the back-end storage subsystem.
The text was updated successfully, but these errors were encountered:
jbaublitz
transferred this issue from stratis-storage/stratis-storage.github.io
Sep 12, 2023
This is primary for the use cases where we expressly have thin-provisioning managed on enterprise SAN storage.
Thin-on-thin is generally not a desirable solution for various reasons, but complicates storage reporting when both are active.
I would request the option to have a storage pool designated as either thick or thin provisioned, though I can understand the issues that might arise with snapshots.
And even though disabling overprivisioning solves some issues, I'd rather have the option of thin-provisioning being completely delegated to the back-end storage subsystem.
The text was updated successfully, but these errors were encountered: