This document details the storage configuration of the Proxmox server.
| Name | Type | Status | Total Size | Used Space | Available Space | % Used |
|---|---|---|---|---|---|---|
| NVME | zfspool | active | 483.7 GB | 134.1 GB | 349.5 GB | 27.73% |
| local | dir | active | 48.2 GB | 17.8 GB | 27.9 GB | 36.92% |
| local-lvm | lvmthin | active | 267.4 GB | 72.4 GB | 195.0 GB | 27.09% |
| proxback | dir | active | 460.4 GB | 224.8 GB | 212.2 GB | 48.82% |
The Proxmox server has the following physical storage devices:
| Device | Model | Size | Usage |
|---|---|---|---|
| sda | SanDisk SDSSDHII480G | 447.1G | Used for proxback backup storage |
| sdb | SanDisk SDSSDA240G | 223.6G | LVM2 member for data volumes |
| sdc | INTEL SSDSA2CW160G3 | 149.1G | System disk with boot and LVM2 member |
| sdd | INRAM SSD 512GB | 476.9G | ZFS mirror member |
| nvme0n1 | HFM512GD3JX013N | 476.9G | ZFS mirror member |
The server uses a ZFS storage pool called "NVME" configured as a mirror (RAID1) between the NVME drive and SSD:
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH
NVME 476G 128G 348G - - 18% 26% 1.00x ONLINE
mirror-0 476G 128G 348G - - 18% 26.9% - ONLINE
nvme-HFM512GD3JX013N_FYA6N030310106B06 477G - - - - - - - ONLINE
ata-INRAM_SSD_512GB_YS000000000000002312 477G - - - - - - - ONLINE
The server uses Logical Volume Management (LVM) for flexible storage allocation:
The system has 2 physical volumes:
| PV | VG | Size | Free | Used |
|---|---|---|---|---|
| /dev/sdb | pve | 223.57 GB | 59.57 GB | 164.00 GB |
| /dev/sdc3 | pve | 148.05 GB | 0 GB | 148.05 GB |
| VG | #PV | #LV | Size | Free |
|---|---|---|---|---|
| pve | 2 | 4 | 371.61 GB | 59.57 GB |
| LV | VG | Type | Size | Data% | Notes |
|---|---|---|---|---|---|
| data | pve | thin-pool | 255.03 GB | 27.09% | Thin provisioning pool |
| root | pve | linear | 47.01 GB | System root filesystem | |
| swap | pve | linear | 8.00 GB | Swap space | |
| vm-100-disk-1 | pve | thin | 273.80 GB | 25.24% | VM disk (from thin pool) |
The system performs regular maintenance on the storage to ensure optimal performance:
/scripts/trim_and_scrub.sh) runs daily at 3:47 AMThe ZFS pool is currently healthy (ONLINE status) with moderate fragmentation (18%).
The logical volumes show appropriate utilization with approximately 27% usage across the thin provisioning pool.