Increase maximum devices per pool from 60 to 200

[1JorgeB]

Merge only after 7.2.1 release.

This was out of date, it mentioned a 60 device pool limit. It was 120, but from 7.2.1 it's going to be 200.

Before Submitting This PR, Please Ensure You Have Completed The Following:

1. Are internal links to wiki documents using relative file links?
2. Are all new documentation files lowercase, with dash separated names (ex. unraid-os.mdx)?
3. Are all assets (images, etc), located in an assets/ subfolder next to the .md/mdx files?
4. Have you checked to ensure there aren't other open Pull Requests for the same update/change?
5. Is the build succeeding?

Summary by CodeRabbit

• Documentation
  • Updated cache pools documentation with increased maximum device count per pool (from 60 to 200 devices).
  • Expanded common use cases section with additional guidance on pool optimization, data protection, workload isolation, and flexible management.

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation update to the cache pools guide for Unraid OS. The maximum device count per pool was increased from 60 to 200 devices, and use-case descriptions were expanded with additional bullets covering pool optimization, data protection, workload isolation, and management flexibility.

Changes

Cohort / File(s)	Change Summary
Documentation Update docs/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx	Updated "Multiple pools" section with revised device limit (60→200) in two locations; expanded "Common use cases" with additional descriptive bullets on optimization, protection, isolation, and flexible management

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verify the accuracy of the increased device limit (200 devices per pool)
• Confirm new use-case descriptions align with current Unraid OS capabilities

Poem

🐰 Two hundred pools now dance in place,
Where sixty used to mark the space—
Our storage docs now gleam so bright,
With optimization, protection, and might!
The burrow expands, efficiency grows,
Cache management wisdom flows.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely summarizes the main change: updating the maximum devices per pool documentation from 60 to 200.
Description check	✅ Passed	The description includes the required pre-submission checklist and provides context about the update timing and the actual limit changes (60→120→200), though checklist items are unchecked.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 053dac6 and 1c6ecc4.

📒 Files selected for processing (1)

• docs/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: deploy-preview

🔇 Additional comments (2)

docs/unraid-os/using-unraid-to/manage-storage/cache-pools.mdx (2)

304-304: Verify AI summary claim about two change locations.

The AI-generated summary states: "Updated the 'Multiple pools' section in two places to reflect a larger maximum device count per pool." However, only line 304 shows a marked change (~) in the provided code.

Please verify whether:

1. A second location mentioning the device limit exists elsewhere in this file and should have been updated, or
2. The AI summary is inaccurate and only one location was actually changed.

---

1-60: Relative file links look good.

The documentation correctly uses relative paths for internal wiki links (e.g., ./array/overview.mdx, ./shares.mdx, ../../advanced-configurations/optimize-storage/zfs-storage.mdx). Pre-submission checklist item appears satisfied.

[github-actions]

PR Preview Action v1.6.2
🚀 View preview at https://unraid.github.io/docs/pr-preview/pr-385/
Built to branch gh-pages at 2025-11-19 17:27 UTC. Preview will be ready when the GitHub Pages deployment is complete.