Skip to content

Fix Fibre Channel redundancy language to match vSAN redundancy level#465

Merged
jasnoyaeger merged 1 commit into
mainfrom
fix/fc-redundancy-language
Jun 2, 2026
Merged

Fix Fibre Channel redundancy language to match vSAN redundancy level#465
jasnoyaeger merged 1 commit into
mainfrom
fix/fc-redundancy-language

Conversation

@jasnoyaeger

@jasnoyaeger jasnoyaeger commented Jun 2, 2026

Copy link
Copy Markdown
Member

Summary

  • The Deduplication tip in docs/product-guide/storage/fibre-channel.md claimed VergeOS "will always store two copies of your data on the FC LUNs," which conflicts with the vSAN redundancy levels doc (N+1 = 2 copies, N+2 = 3 copies).
  • Updated the language to state that VergeOS replicates data across FC LUNs according to the configured vSAN redundancy level, with a link to the redundancy levels page.

Test plan

  • Verify rendered page on local mkdocs serve at /product-guide/storage/fibre-channel/
  • Confirm the inline link to /product-guide/storage/vsan-redundancy-levels resolves correctly
  • Confirm no conflict remains between the FC doc and the vSAN redundancy levels doc

🤖 Generated with Claude Code

The Deduplication tip incorrectly stated VergeOS always stores two
copies on FC LUNs, which conflicts with the vSAN redundancy levels
doc (N+1=2 copies, N+2=3 copies). Updated to reference the configured
redundancy level instead.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@jasnoyaeger jasnoyaeger merged commit 8f4cb34 into main Jun 2, 2026
3 checks passed
@jasnoyaeger jasnoyaeger deleted the fix/fc-redundancy-language branch June 2, 2026 15:46
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