DOCS-2594 / 27 / DOCS-2594-correct-fusion-pools-content-to-indicate-spares-only-allocate-to-data-vdev#4635
Conversation
bugclerk
changed the title
Vale Style Guide Issues (Previous - Click to expand)Vale Style Guide Issues📊 Summary: 16 issues found in changed files - 0 errors, 0 warnings, 16 suggestions Changed files with issues: static/includes/FusionPoolsCommonContent.md (16 issues)
🔧 To fix: Review the issues above and update your documentation accordingly. |
…indicate-spares-only-allocate-to-data-vdev
Vale Style Guide Issues (Previous - Click to expand)Vale Style Guide Issues📊 Summary: 16 issues found in changed files - 0 errors, 0 warnings, 16 suggestions Changed files with issues: static/includes/FusionPoolsCommonContent.md (16 issues)
🔧 To fix: Review the issues above and update your documentation accordingly. |
micjohnson777
left a comment
micjohnson777
left a comment
There was a problem hiding this comment.
Metadata is now call Special so this needs to be updated to reflect that change in 26.
micjohnson777
added
the
Technical Writer Review (MJ)
That's not what I'm seeing in BETA.2? 
|
…indicate-spares-only-allocate-to-data-vdev
Vale Style Guide Issues📊 Summary: 16 issues found in changed files - 0 errors, 0 warnings, 16 suggestions Changed files with issues: static/includes/FusionPoolsCommonContent.md (16 issues)
🔧 To fix: Review the issues above and update your documentation accordingly. |
3 participants
static/includes/FusionPoolsCommonContent.md:
activate only in data VDEVs, so the special VDEV must have its own internal redundancy. Kept the pool-corruption
consequence and the drive-type-choice point (lines 11-12).
Thanks for contributing to TrueNAS documentation! By opening a Pull Request, you're acknowledging that your changes will be distributed under the Creative Commons 4.0 license.