Skip to content

docs(kb): vSAN "because tier N slow" messages and the tier's drive class - #502

Closed
CarlRodabaugh wants to merge 1 commit into
mainfrom
docs/kb-vsan-tier1-drive-class
Closed

CarlRodabaugh wants to merge 1 commit into
mainfrom
docs/kb-vsan-tier1-drive-class

Conversation

@CarlRodabaugh

Copy link
Copy Markdown
Collaborator

Summary

New KB article: knowledge-base/posts/vsan-tier1-slow-drive-class.md.

Covers repeated vSAN [JOURNAL] ... because tier N slow and Slow write to tier <T>, <N> ms. messages alongside short VM stalls that users can report as network timeouts.

  • explains the messages as the named tier lagging on writes, with several possible causes (failing drive, nearly full tier, scheduled load, drive class not fitting the tier), and tells readers to investigate the tier the message names
  • check steps: named tier, the VM drive's Preferred Tier (as intended placement, not proof of where blocks sit), capacity, SMART, tier drive list and models, endurance class, a log spot-check, then a system diagnostics report
  • the reallocated-sectors note: default maximum is 1, so two or more sectors raise the warning; a small count is evidence of degradation to weigh, not proof of cause
  • resolution routes drive purchases and removals through Support as one planned job, per Scaling Down a vSAN

Docs conflict to note: Storage Tiers describes Tier 1 as high-endurance NVMe, while the Node Sizing Guide permits enterprise SAS/SATA SSDs in a primary tier that meet its 1 DWPD floor. The article states both and tells readers to confirm the design with Support. A separate docs issue will track reconciling the two pages.

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)
  • Tier descriptions, sizing wording, the Advanced settings path, and the 80% High Usage default checked against the live pages
  • Technical review against current docs and 26.2.2.1 application source, including the reallocated-sector comparison
  • Not run locally: mkdocs build / lychee (CI covers those)

🤖 Generated with Claude Code

…r drive class)

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

Copy link
Copy Markdown
Collaborator Author

Superseded by verge-io/docs-vergeos#91.

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