Repository navigation
docs(kb): vSAN "No space left on device" while tier shows free space (mixed drive sizes) - #500
Closed
CarlRodabaugh wants to merge 1 commit into
Closed
CarlRodabaugh wants to merge 1 commit into
CarlRodabaugh wants to merge 1 commit into
Conversation
…(mixed drive sizes) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Collaborator
Author
|
Superseded by verge-io/docs-vergeos#89. This PR was opened in the legacy documentation repository. The article has been recreated in the repository that supplies docs.verge.io, using its current structure. |
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
New KB article:
knowledge-base/posts/vsan-mixed-drive-sizes-no-space-left.md.vSAN writes fail with
(28) No space left on deviceand VMs stop while the tier's usage percentage still looks healthy, because the tier mixes drive sizes and can only use each drive up to the size of the smallest one. This keeps coming up in support, and the only public coverage is the one-line rule in Scaling Up a vSAN. The article covers:ybvsan/appserverlog lines (ids sanitized), so the page is findable by error string, plus the outgoing-sync error with a note that a full receiving system produces it tooVerification
python .github/scripts/validate_frontmatter.py: passpython .github/scripts/validate_widget_links.py: passcurl -sIL)vsan_used/vsan_maxconfirmed through the API on a 26.2 systemmkdocs build/ lychee locally (CI covers those)🤖 Generated with Claude Code