StorPool FAQ
Here you can find answers for some of the most frequently asked questions about StorPool.
- Common
- What is the upgrade policy and compatibility between versions?
- How to calculate the estimate usable disk space for a hybrid cluster?
- What is the current capacity, provisioned and available space in the cluster?
- What is the current thin provisioning gain of the cluster?
- How does StorPool handle writes?
- Why are there partitions on all SATA drives used by StorPool?
- Why the StorPool processes seem to be at 100% CPU usage all the time?
- What addresses uses StorPool for monitoring
- What is required when I add/change memory modules on a hypervisor?
- What happened to the User guide
- Exceptions
- Onapp integration
- Erasure coding
- Is Erasure Coding enabled for a whole cluster, or is it enabled on a per-volume basis?
- Are there any expected performance issues that need to be considered?
- What hardware configurations are supported?
- What are the supported erasure coding schemes and their respective overheads?
- Do the required regular snapshots offset some of the space savings?
- Would I need additional space from triple replication to erasure coding during the conversion?
- Is there an ideal minimum volume size?
- How frequently does StorPool recalculate the parity blocks - with each change of the data blocks, or with another method?
- What is the impact of erasure coding on the network load?
- Is there a difference between the performance of the different erasure coding schemes?
- Is there any delay in user operations when regular snapshots are being created?
- What are the chances that erasure coding can’t recover from a disk failure?
- How much is the used and free space?