Repository navigation
Conversation
Document the stale extent exposure in the current thick-LV design and propose a zero-enabled, non-overcommitted thin-pool architecture with preserved NVMe striping. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
ganesan23
requested review from
a team,
Simon Croome (croomes),
jmclong (jmclong) and
Lana Andreasyan (landreasyan)
as code owners
September 9, 2026 20:05
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Motivation
The current driver removes ordinary thick LVs without sanitizing all released extents. A later raw-block volume can receive those extents and potentially observe data written by a previous tenant. Thin-pool allocation-time zeroing can provide logical reuse isolation, but adopting it safely requires more than changing the
lvcreatecommand.Review focus
Testing
Documentation-only change; no runtime behavior changed.