Record the two shrink facts measured in #97 - #98
Merged
Conversation
SizeMax includes the unallocated run behind the partition, and -UseMaximumSize takes the largest run on the whole disk. Neither is documented by Microsoft, both cost real time to find, and neither was anywhere a clone can see them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Seven lines in
AGENTS.md.Both were measured while fixing #83, neither is documented by Microsoft, and until now both lived only in a git-ignored plan file — so a clone carried none of it.
Get-PartitionSupportedSize'sSizeMaxis the partition's size plus the contiguous unallocated run right behind it. A shrink target taken from it gives up less than was asked, or grows the volume.New-Partition -UseMaximumSizecreates the largest partition on the whole disk, not one in the space just freed, so a shrink can leave that space unused.-Offsetmust be aligned up to a whole megabyte: any other offset is refused outright, andResize-Partitionaligns to the cluster, landing a few hundred bytes off.🤖 Generated with Claude Code