Skip to main content

Proxmox ZFS & Hardware RAID Capacity Calculator

Calculate net usable Proxmox VE ZFS capacity, padding loss, slop space, 80% safe ceiling, ARC RAM, and zpool create CLI script.

Input Parameters

Try Example:
1128
0.11000

Calculation Results

Total Number of Disks
6 Disks
Capacity per Disk
4
Capacity Unit
TB
ZFS VDEV Topology
raidz2
Storage Media Type
ssd
Disk Media Specification
Enterprise SSD
Number of VDEV Stripes
1 VDEVs
Sector Ashift Value
12
ZFS Recordsize
128 KiB
ZFS Pool Name
rpool-data
Total Raw Capacity (Decimal)
24 TB
Total Raw Capacity (Binary)
21.83 TiB
Standard RAID Usable (Decimal)
16 TB
Standard RAID Usable (Binary)
14.55 TiB
Parity & Hot Spare Allocation
8 TB
ZFS Sector Padding Overhead
0.45 TB
ZFS Slop Space Reservation (1/32)
0.137 TB
ZFS Net Usable Capacity (Decimal)
15.41 TB
ZFS Net Usable Capacity (Binary)
14.02 TiB
ZFS 80% Safe Capacity Limit (TB)
12.33 TB
ZFS 80% Safe Capacity Limit (TiB)
11.21 TiB
Disk Fault Tolerance
2 drive per VDEV bersamaan
Estimated Read Performance Gain
4×
Estimated Write Performance Gain
1×
Estimated Random Read IOPS
32,000 IOPS
Estimated Random Write IOPS
6,800 IOPS
Minimum ZFS ARC RAM
26 GB
Recommended Production ZFS ARC RAM
32 GB
Want to compare 2 design options side-by-side (e.g., Scenario A vs Scenario B)?
⚡ Server & Storage Hardware Advisory
HBA LSI 9300-8i / 9400-16i (IT-Mode Non-RAID) + ECC RAM
Enterprise CMR Drives / Datacenter NVMe (PLP Power-Loss Protection)

For Proxmox ZFS, always use IT-Mode HBA controllers instead of hardware RAID cards, paired with Pure Sinewave UPS.

Terminal Configuration Script (CLI)
# =====================================================================
# InfraCalc.web.id — ZFS Pool untuk Proxmox VE | Topologi: RAIDZ2 | 6 Drive (24 TB Raw)
# Kapasitas Bersih ZFS: 15.41 TB (14.02 TiB) | Batas Aman 80%: 12.33 TB (11.21 TiB)
# Ganti ID DISK dengan ID asli dari: ls -l /dev/disk/by-id/ (hindari nama /dev/sdX)
# =====================================================================

# 1. Buat ZFS Storage Pool di Terminal Proxmox VE
zpool create -f -o ashift=12 -O compression=zstd -O acltype=posixacl -O xattr=sa -O normalization=formD rpool-data \
  raidz2 /dev/disk/by-id/nvme-DISK_1 /dev/disk/by-id/nvme-DISK_2 /dev/disk/by-id/nvme-DISK_3 /dev/disk/by-id/nvme-DISK_4 /dev/disk/by-id/nvme-DISK_5 /dev/disk/by-id/nvme-DISK_6

# 2. Rekomendasi Dataset Options untuk Proxmox VM & Container
zfs set recordsize=128k rpool-data
zfs set atime=off rpool-data

# 3. Verifikasi Status Pool
zpool status rpool-data
zfs list rpool-data
2D Rack Elevation Builder

Visual 2D 19" Server Rack & Patch Panel Builder

24U Standing Close Rack 19" — 11U Used / 13U Airflow Free24U24U23U23U22U22U21U21U20U20U19U19U18U18U17U17U16U16U15U15U14U14U13U13U12U12U11U11U10U10U9U9U8U8U7U7U6U6U5U5U4U4U3U3U2U2U1U1U2U Online Sinewave Rackmount UPS2200 VA • Pure Sinewave • LCD2U2U External VRLA Battery Bank (EBM)65 Ah Deep-Cycle • Hot-Swappable2U2U ZFS / Hardware Storage Server (RAIDZ2)8x 4 TB Hot-Swap Bays • Redundant PSU2U1U Proxmox VE Compute Hypervisor Node1U1U Horizontal Brush Cable Management Panel1U1U 24-Port Cat6 Shielded Patch Panel1U1U 24-Port Gigabit PoE+ / L3 Core Switch1U1U Rackmount Metered PDU (8x C13 Outlet)1U
Rack Capacity & Thermal Summary
Occupied U11U / 24U
Free Airflow13U Free
Estimated Total Rack Weight± 138 kg
Rack Mounting Best Practices
  • 1U–4U (Bottom): Heavy UPS & VRLA Battery Banks mounted at the bottom to lower center of gravity.
  • Middle: Compute servers, ZFS storage arrays, and NVRs placed in the center cold-aisle zone.
  • Top: Top-of-Rack PoE switches, Cat6 patch panels, and brush organizers for overhead cable trays.
Procurement BoQ & Cost Estimator

Generate Project BoQ / Cost Estimate (RAB)

KodeMaterial & EquipmentQty (+15%)UnitUnit Price (IDR)Line Total (IDR)
UPS-UNIT
Online Pure Sinewave Rackmount UPS (2200 VA)
Pure Sinewave, PF 0.8–0.9, AVR
1UnitRp 6.800.000
BATT-VRLA
12V VRLA Deep-Cycle Battery Bank (~100 Ah Total)
Maintenance-Free VRLA Battery
2UnitRp 3.700.000
SRV-DISK
Enterprise NAS / Server Storage Drive & Railkit
CMR 7200 RPM 24/7 Enterprise Grade
4UnitRp 11.800.000
RACK-PDU
19" Server Rack Cabinet + Metered PDU + C13/C14 Cords
Includes grounding bar & roof fan unit
2(Base: 1)PaketRp 9.700.000
Equipment & Material Subtotal:Rp 32.000.000
Estimated Installation & Commissioning (10%):Rp 3.200.000
PPN (11%):Rp 3.872.000
ESTIMATED GRAND TOTAL:Rp 39.072.000

Note: Unit prices above are initial reference estimates and can be edited inline.Referensi Teknis & BoQ — Built for Network & System Engineers

Share to WhatsApp
ℹ️

Technical Accuracy Note: Calculation results are engineering estimates based on standard RFC/IEEE/ITU-T models. Actual field performance may vary due to protocol overhead, hardware specifications, and environmental factors.

🚀 Share Calculation Results or Embed on Your Site

Deep-link automatically preserves your current inputs — ideal for WhatsApp, Telegram, Reddit, or engineering docs.

How to Use This Tool

  1. Select your drive count, individual disk capacity (TB or GB), and target ZFS topology (Mirror / RAID 10, RAIDZ1, RAIDZ2, or RAIDZ3).
  2. Specify the pool ashift (ashift 12 for modern 4K disks), dataset recordsize (128 KiB standard, 16 KiB database, or 1024 KiB backup), and storage media type (NVMe, SSD, or HDD).
  3. Inspect the net usable ZFS capacity, the 80% performance threshold, estimated IOPS, and ARC RAM requirements, then copy the zpool create command into your Proxmox VE shell.

Worked Example: Proxmox Standard 6 × 4 TB RAIDZ2

Computed example: An array of 6 drives × 4 TB (24 TB / 21.83 TiB raw) in RAIDZ2 yields a net ZFS usable capacity of 15.41 TB (14.02 TiB) after parity, padding loss (0.45 TB), and slop space (0.1374 TB). The 80% safe capacity ceiling is 12.33 TB (11.21 TiB) with a minimum ARC RAM requirement of 26 GB (host recommendation 32 GB).

Example Input
Total Physical Drives
6 Disks
Capacity per Drive
4
Capacity Unit
TB (Decimal Terabyte 10^12)
ZFS Redundancy Topology
RAIDZ2 (Dual Parity — Production Recommended)
Pool ashift (Sector Alignment)
ashift 12 (4 KiB — Modern NVMe/SSD/HDD standard)
Dataset recordsize
128 KiB (Default ZFS & Proxmox General)
Storage Media Type
Enterprise SATA/SAS SSD (~8,000 IOPS)
Proxmox ZFS Pool Name
rpool-data
Calculated Output
Total Number of Disks
6 Disks
Capacity per Disk
4
Capacity Unit
TB
ZFS VDEV Topology
raidz2
Storage Media Type
ssd
Disk Media Specification
Enterprise SSD
Number of VDEV Stripes
1 VDEVs
Sector Ashift Value
12
ZFS Recordsize
128 KiB
ZFS Pool Name
rpool-data
Total Raw Capacity (Decimal)
24 TB
Total Raw Capacity (Binary)
21.83 TiB
Standard RAID Usable (Decimal)
16 TB
Standard RAID Usable (Binary)
14.55 TiB
Parity & Hot Spare Allocation
8 TB
ZFS Sector Padding Overhead
0.45 TB
ZFS Slop Space Reservation (1/32)
0.137 TB
ZFS Net Usable Capacity (Decimal)
15.41 TB
ZFS Net Usable Capacity (Binary)
14.02 TiB
ZFS 80% Safe Capacity Limit (TB)
12.33 TB
ZFS 80% Safe Capacity Limit (TiB)
11.21 TiB
Disk Fault Tolerance
2 drive per VDEV bersamaan
Estimated Read Performance Gain
4×
Estimated Write Performance Gain
1×
Estimated Random Read IOPS
32,000 IOPS
Estimated Random Write IOPS
6,800 IOPS
Minimum ZFS ARC RAM
26 GB
Recommended Production ZFS ARC RAM
32 GB
Terminal Configuration Script (CLI)
# ===================================================================== # InfraCalc.web.id — ZFS Pool untuk Proxmox VE | Topologi: RAIDZ2 | 6 Drive (24 TB Raw) # Kapasitas Bersih ZFS: 15.41 TB (14.02 TiB) | Batas Aman 80%: 12.33 TB (11.21 TiB) # Ganti ID DISK dengan ID asli dari: ls -l /dev/disk/by-id/ (hindari nama /dev/sdX) # ===================================================================== # 1. Buat ZFS Storage Pool di Terminal Proxmox VE zpool create -f -o ashift=12 -O compression=zstd -O acltype=posixacl -O xattr=sa -O normalization=formD rpool-data \ raidz2 /dev/disk/by-id/nvme-DISK_1 /dev/disk/by-id/nvme-DISK_2 /dev/disk/by-id/nvme-DISK_3 /dev/disk/by-id/nvme-DISK_4 /dev/disk/by-id/nvme-DISK_5 /dev/disk/by-id/nvme-DISK_6 # 2. Rekomendasi Dataset Options untuk Proxmox VM & Container zfs set recordsize=128k rpool-data zfs set atime=off rpool-data # 3. Verifikasi Status Pool zpool status rpool-data zfs list rpool-data

Core Concept & Engineering Notes

OpenZFS on the Proxmox VE virtualization platform is an advanced enterprise file system and logical volume manager combining RAID data redundancy with cryptographic end-to-end data integrity through automatic self-healing checksums. Unlike legacy hardware RAID controllers that estimate net capacity by simply subtracting dedicated parity disks, OpenZFS incorporates internal allocation dynamics that dictate actual usable capacity for virtual machines and LXC containers. The first structural overhead is sector alignment padding loss. When configuring RAIDZ topologies with an ashift of 12 (4 KiB native sectors) or ashift of 13 (8 KiB sectors), dataset records are partitioned across vdev member drives in strict multiples of the underlying sector size. Sub-optimal drive counts or small record sizes (such as 8 KiB or 16 KiB optimized for transactional databases) can introduce 4% to 8% in sector padding inefficiencies. The second layer is OpenZFS Slop Space Allocation, a reserved pool margin representing 1/32 (3.125%) of total raw storage (capped at 128 GiB) reserved by the ZFS kernel to guarantee that copy-on-write operations, file deletions, and snapshot destaging complete without deadlocking an exhausted pool. The third and most operationally vital constraint is the 80% Safe Capacity Rule. Because ZFS relies on a Copy-on-Write (CoW) transactional engine, operating a storage pool beyond 80% of its physical capacity degrades contiguous free space into fine fragmentation. This collapses write IOPS throughput and escalates I/O wait latency across all guest VMs. This calculator accounts for all these overhead layers, computes recommended host Adaptive Replacement Cache (ARC) memory requirements, and generates production-grade zpool creation scripts referencing persistent disk IDs.

How It Was Calculated (Formulas & Steps)

Frequently Asked Questions (FAQ)

Why is the usable ZFS capacity in Proxmox smaller than standard hardware RAID?

Beyond the ~9% difference between decimal TB (10^12) and binary TiB (2^40) reported by the OS, ZFS reserves Slop Space (1/32 of pool size, up to 128 GiB), sector padding alignment margins on RAIDZ, and internal copy-on-write metadata structures.

Why is it strongly advised never to fill a ZFS pool beyond 80% capacity?

Because ZFS is a Copy-on-Write filesystem. When free capacity drops below 20%, the kernel switches from a high-speed first-fit block allocator to an exhaustive best-fit allocator, escalating fragmentation and drastically depressing write performance.

How much RAM does Proxmox VE require for the ZFS ARC cache?

The standard sizing guideline is 2 GB base RAM for the Proxmox OS plus 1 GB of RAM per 1 TB of raw pool capacity. If inline deduplication is enabled, RAM requirements jump dramatically to at least 5 GB per 1 TB of storage to hold the DDT table in memory.

Why should we always use `/dev/disk/by-id/` rather than `/dev/sda` device names in Proxmox?

Linux device letters such as `/dev/sda` or `/dev/sdb` are dynamically assigned during kernel boot and can shuffle upon reboot or controller port re-cabling. Using persistent `/dev/disk/by-id/` paths binds drives to their permanent serial numbers, preventing failed pool imports.

References & Notes

Last updated: Technically Verified · Industry Standard

Note: Results above are mathematical estimates based on standard formulas. Always verify against official vendor documentation and site conditions before production deployment.

🔗Related Scenarios & Companion Calculators

Browse All 30+ Scenarios →
🔬 Scientific Methodology & Normative Verification

Engineering Sensitivity Analysis, Response Curve & Technical Citation

✓ Calibrated to ISO/IEC/IEEE/TIA Clauses

1. 1. 3-Point Engineering Sensitivity & Tolerance Envelope

Comparative evaluation across theoretical laboratory bounds (0% loss), current nominal operating point, and conservative field safety bounds (±15% thermal/aging derating).

Evaluated Parameter Ideal Theoretical Bound Nominal Operating Point Conservative Safety Bound (±15%) Engineering Derating Rule
Total Number of Disks 5.4 6 6.9 Engineering Safety Margin (+15% Overhead)
Capacity per Disk 3.6 4 4.6 Engineering Safety Margin (+15% Overhead)
Number of VDEV Stripes 0.9 1 1.15 Engineering Safety Margin (+15% Overhead)
Sector Ashift Value 10.8 12 13.8 Engineering Safety Margin (+15% Overhead)
ZFS Recordsize 115 128 147 Engineering Safety Margin (+15% Overhead)

2. 2. Mathematical Function Curve & Operating Coordinate (x₀, y₀)

MATHEMATICAL RESPONSE CURVE: TOTAL NUMBER OF DISKS VS TOTAL NUMBER OF DISKS Conservative Engineering Bound (+15% Safety Margin) 2.4 3.6 4.8 6 7.2 8.4 9.6 (x₀=6, y₀=6) Variabel Independen (x): Total Number of Disks

3. 3. Physical Constants & Normative Standard Clauses

k_IEC(10¹²/2⁴⁰) = 0.9094947 TiB/TB ISO/IEC 80000-13:2008

Decimal Terabyte (SI) to Binary Tebibyte (IEC) Conversion Ratio

Clause 4 — Binary Prefixes — 1 TB = 10¹² Bytes; 1 TiB = 2⁴⁰ Bytes = 1,099,511,627,776 Bytes.

α_Cu(20°C) = 0.00393 °C⁻¹ IEC 60028

Temperature Coefficient of Resistance for Copper

International Annealed Copper Standard — Used in thermal derating equation: R(T) = R_20 × [1 + 0.00393 × (T - 20)].

4. 4. Independent Technical & Academic Citation (IEEE / APA 7th / BibTeX / LaTeX)

Use the standard citation formats below to reference this computational methodology in engineering specifications, audit reports, or academic papers.

Format IEEE & APA 7th Edition

[IEEE] KalkuNet Engineering Team, "Proxmox ZFS & Hardware RAID Capacity Calculator — Standard Engineering Computational Instrument," KalkuNet Technical Suite, 2026. [Online]. Available: https://kalkunet.com/en/tools/zfs-raid-calculator. [Accessed: 2026-11-08].

[APA 7th] KalkuNet Engineering Team. (2026). Proxmox ZFS & Hardware RAID Capacity Calculator (Production release 2026-11-08) [Engineering computational software]. KalkuNet. https://kalkunet.com/en/tools/zfs-raid-calculator

BibTeX & LaTeX Derivation Snippet
@software{kalkunet_zfs_raid_calculator_2026,
  author = {{KalkuNet Engineering Team}},
  title = {{Proxmox ZFS & Hardware RAID Capacity Calculator --- KalkuNet Engineering Suite}},
  year = {2026},
  publisher = {KalkuNet.com},
  url = {https://kalkunet.com/en/tools/zfs-raid-calculator},
  urldate = {2026-11-08}
}

% LaTeX Engineering Derivation — Generated via https://kalkunet.com/en/tools/zfs-raid-calculator
\begin{equation}
  \text{Model: } Gross Raw Capacity (TB) = Drive Count × Capacity per Drive
\end{equation}
% Parameter Input Terukur: drives = 6, \; driveSize = 4, \; unit = TB, \; topology = raidz2
% Hasil Evaluasi Numerik : totalDrives = \mathbf{6}, \; driveSize = \mathbf{4}, \; unit = \mathbf{TB}