Skip to content

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
mainfrom
docs/kb-vsan-mixed-drive-sizes
Closed

CarlRodabaugh wants to merge 1 commit into
mainfrom
docs/kb-vsan-mixed-drive-sizes

Conversation

@CarlRodabaugh

Copy link
Copy Markdown
Collaborator

Summary

New KB article: knowledge-base/posts/vsan-mixed-drive-sizes-no-space-left.md.

vSAN writes fail with (28) No space left on device and 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:

  • the verbatim ybvsan / appserver log 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 too
  • why it happens, citing Scaling Up a vSAN (smallest-drive rule) and vSAN Architecture (even distribution across nodes), with a raw-space estimate labeled as a planning approximation
  • how to confirm it from each drive's vSAN used and max values rather than the tier percentage, and how to read the tier status fields without treating them as proof
  • freeing space now (snapshot review with the mid-sync deletion warning, background reclamation, Discard plus a guest TRIM) and fixing it long term (balanced, consistently sized additions; per-drive headroom for the 30% rule; drive removal through support per the Scale Up SOP)

Verification

  • python .github/scripts/validate_frontmatter.py: pass
  • python .github/scripts/validate_widget_links.py: pass
  • All linked docs.verge.io URLs return 200 (curl -sIL)
  • Each attributed claim checked against the linked page in this repo and on the live site
  • Technical review against current docs and 26.2.2.1 application source; per-drive vsan_used / vsan_max confirmed through the API on a 26.2 system
  • Not checked: the per-drive used/max labels in the 26.1.8 UI, and mkdocs build / lychee locally (CI covers those)

🤖 Generated with Claude Code

…(mixed drive sizes)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@CarlRodabaugh

Copy link
Copy Markdown
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.

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.

1 participant