ZFSSA Storage Expansion Behavior
(Doc ID 2203416.1)
Last updated on DECEMBER 05, 2021
Applies to:
Oracle ZFS Storage ZS3-2 - Version All Versions and laterOracle ZFS Storage ZS3-4 - Version All Versions and later
Oracle ZFS Storage ZS3-BA - Version All Versions and later
Oracle ZFS Storage ZS4-4 - Version All Versions and later
Sun ZFS Storage 7120 - Version All Versions and later
7000 Appliance OS (Fishworks)
Goal
The goal of this document is to better understand:
- How to grow storage from BUI and CLI on ZFSSA
- After-effects and limitations of growing storage
- Specific behavior to following profiles and ways to workaround the spare-hungry algorithm when growing storage
- - mirror
- - three way mirror
- - single-parity RAID
- - double-parity RAID
- - triple-parity RAID
Terminology:
| N | = Number of disks |
| BD | = Base disks (i.e., number of disks in initial pool configuration) |
| AD | = Additional disks (i.e., number of disks being added while expanding storage) |
| TB | = Terabytes of raw capacity (1000^4 = 1,000,000,000,000 bytes) |
| TiB | = Terabytes of usable capacity (1024^4 = 1,099,511,627,776 bytes) |
Assumptions:
When this document refers to disks, that means data disks and not log, cache, or spare devices.
Although this information can be applied to data disks of any size, the examples assume data disks are 2TB.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |