Unless I'm reading the hdsize option wrong (only use this size leave the rest unpartioned) then this isn't the behaviour I would expect.
I'm planning to install on an SSD and leave enough room for 2 ceph journal partitions.
Size is 200GB - no matter what I set the hdsize option to it always creates sda3 as the largest remaining amount
I specified a HDSIZE of 60 and this is what it does:
`-sda3 8:3 0 199.9G 0 part
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
fd0 2:0 1 4K 0 disk
sda 8:0 0 200G 0 disk
|-sda1 8:1 0 1007K 0 part
|-sda2 8:2 0 127M 0 part
`-sda3 8:3 0 199.9G 0 part
|-pve-root 252:0 0 10G 0 lvm /
|-pve-swap 252:1 0 4G 0 lvm [SWAP]
`-pve-data 252:2 0 38.5G 0 lvm /var/lib/vz
Which means I have no space left to create my journals.
I've played with all other sizes and no matter what - sda3 is always 199.9G with various different LVM sizes below.
I would expect if I specify 170 as hdsize something similar to above but with sda3 being 169.9G
Am I reading this parameter wrong? I would prefer to use the installer and not have to go jessie -- pve route.
Thanks
Brian
I'm planning to install on an SSD and leave enough room for 2 ceph journal partitions.
Size is 200GB - no matter what I set the hdsize option to it always creates sda3 as the largest remaining amount
I specified a HDSIZE of 60 and this is what it does:
`-sda3 8:3 0 199.9G 0 part
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
fd0 2:0 1 4K 0 disk
sda 8:0 0 200G 0 disk
|-sda1 8:1 0 1007K 0 part
|-sda2 8:2 0 127M 0 part
`-sda3 8:3 0 199.9G 0 part
|-pve-root 252:0 0 10G 0 lvm /
|-pve-swap 252:1 0 4G 0 lvm [SWAP]
`-pve-data 252:2 0 38.5G 0 lvm /var/lib/vz
Which means I have no space left to create my journals.
I've played with all other sizes and no matter what - sda3 is always 199.9G with various different LVM sizes below.
I would expect if I specify 170 as hdsize something similar to above but with sda3 being 169.9G
Am I reading this parameter wrong? I would prefer to use the installer and not have to go jessie -- pve route.
Thanks
Brian