rpool data size

SamTzu

Active Member
When I created a ZFS raid Proxmox allocated 13T out of 28T to data (ie. local-zfs).
How do I increase the size allocated to data?

Code:
zfs list
NAME                           USED  AVAIL     REFER  MOUNTPOINT
rpool                         19.7T   805G      151K  /rpool
rpool/ROOT                    64.1G   805G      140K  /rpool/ROOT
rpool/ROOT/pve-1              64.1G   805G     64.1G  /
rpool/data                    13.0T   805G      151K  /rpool/data
 

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
7,628
1,441
164
please post the full output of 'zfs list -o space,refquota,quota,volsize'
 

SamTzu

Active Member
It's odd. The usage of local-zfs keeps changing depending on my actions.
Yesterday I purged a 5Tb VM and it showed only 13Tib as the size of storage space. Now it shows size 20.4Tib.

zfs list -o space,refquota,quota,volsize
NAME AVAIL USED USEDSNAP USEDDS USEDREFRESERV USEDCHILD REFQUOTA QUOTA VOLSIZE
rpool 8.16T 12.3T 0B 151K 0B 12.3T none none -
rpool/ROOT 8.16T 64.1G 0B 140K 0B 64.1G none none -
rpool/ROOT/pve-1 8.16T 64.1G 0B 64.1G 0B 0B none none -
rpool/data 8.16T 12.3T 0B 151K 0B 12.3T none none -
rpool/data/subvol-100-disk-0 7.55G 461M 0B 461M 0B 0B 8G none -
rpool/data/subvol-101-disk-0 750G 12.3T 0B 12.3T 0B 0B 13.0T none -

______________________________________________________

Usage
60.04% (12.26 TiB of 20.42 TiB

_______________________________________________________


fdisk -l
Disk /dev/sda: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000AS0002-1NA
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: FCE77EDC-2FEF-4D9E-8B5C-DA0F4190FB0D

Device Start End Sectors Size Type
/dev/sda1 34 2047 2014 1007K BIOS boot
/dev/sda2 2048 1050623 1048576 512M EFI System
/dev/sda3 1050624 15628053134 15627002511 7.3T Solaris /usr & Apple ZFS

Partition 1 does not start on physical sector boundary.


Disk /dev/sdb: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000AS0002-1NA
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 044BF401-63BB-487C-B438-1AC28C239062

Device Start End Sectors Size Type
/dev/sdb1 34 2047 2014 1007K BIOS boot
/dev/sdb2 2048 1050623 1048576 512M EFI System
/dev/sdb3 1050624 15628053134 15627002511 7.3T Solaris /usr & Apple ZFS

Partition 1 does not start on physical sector boundary.


Disk /dev/sdc: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000DM004-2CX1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 3C0B2EB9-C9E6-42C6-A98F-7905DB450DAD

Device Start End Sectors Size Type
/dev/sdc1 34 2047 2014 1007K BIOS boot
/dev/sdc2 2048 1050623 1048576 512M EFI System
/dev/sdc3 1050624 15628053134 15627002511 7.3T Solaris /usr & Apple ZFS

Partition 1 does not start on physical sector boundary.


Disk /dev/sdd: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000DM004-2CX1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 1BBB7C2A-7722-4E31-A4CB-F053438B32C7

Device Start End Sectors Size Type
/dev/sdd1 34 2047 2014 1007K BIOS boot
/dev/sdd2 2048 1050623 1048576 512M EFI System
/dev/sdd3 1050624 15628053134 15627002511 7.3T Solaris /usr & Apple ZFS

Partition 1 does not start on physical sector boundary.


Disk /dev/sdf: 7.5 GiB, 8011120640 bytes, 15646720 sectors
Disk model: DataTraveler 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x67ec1d41

Device Boot Start End Sectors Size Id Type
/dev/sdf1 2048 15646719 15644672 7.5G 82 Linux swap / Solaris
 

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
7,628
1,441
164
yes, for a PVE storage we calculate total capacity by adding used and available storage. that means the total capacity can change even if the pool remains the same.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!