Just some additional information - when two disks are provided during deploy, LV is spread across both as expected. It is just adding a block device which does not enlarge LV ^^^
juju ssh cinder/5 "lsblk; sudo vgs; sudo lvs" NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 50G 0 disk └─sda1 8:1 0 50G 0 part / sdb 8:16 0 10G 0 disk ├─cinder--volumes-cinder--volumes--pool_tmeta 252:0 0 20M 0 lvm │ └─cinder--volumes-cinder--volumes--pool 252:2 0 19G 0 lvm └─cinder--volumes-cinder--volumes--pool_tdata 252:1 0 19G 0 lvm └─cinder--volumes-cinder--volumes--pool 252:2 0 19G 0 lvm sdc 8:32 0 10G 0 disk └─cinder--volumes-cinder--volumes--pool_tdata 252:1 0 19G 0 lvm └─cinder--volumes-cinder--volumes--pool 252:2 0 19G 0 lvm VG #PV #LV #SN Attr VSize VFree cinder-volumes 2 1 0 wz--n- 19.99g 984.00m LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert cinder-volumes-pool cinder-volumes twi-a-tz-- 18.99g 0.00 0.55
Just some additional information - when two disks are provided during deploy, LV is spread across both as expected. It is just adding a block device which does not enlarge LV ^^^
juju ssh cinder/5 "lsblk; sudo vgs; sudo lvs" -volumes- cinder- -volumes- -pool_tmeta 252:0 0 20M 0 lvm -volumes- cinder- -volumes- -pool 252:2 0 19G 0 lvm -volumes- cinder- -volumes- -pool_tdata 252:1 0 19G 0 lvm -volumes- cinder- -volumes- -pool 252:2 0 19G 0 lvm -volumes- cinder- -volumes- -pool_tdata 252:1 0 19G 0 lvm -volumes- cinder- -volumes- -pool 252:2 0 19G 0 lvm volumes- pool cinder-volumes twi-a-tz-- 18.99g 0.00 0.55
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 50G 0 disk
└─sda1 8:1 0 50G 0 part /
sdb 8:16 0 10G 0 disk
├─cinder-
│ └─cinder-
└─cinder-
└─cinder-
sdc 8:32 0 10G 0 disk
└─cinder-
└─cinder-
VG #PV #LV #SN Attr VSize VFree
cinder-volumes 2 1 0 wz--n- 19.99g 984.00m
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
cinder-