Hi Alex,
The step I took as 'juju add-disk ceph-osd devices='/dev/nvme6p1'. This step failed as there was no room in the bluestore to add another db & wal lvm.
This made the disk /dev/nvme6p1 unusable and to get is back to a state in where I could re-add it to the charm, I had to take the following actions:
* lvremove -v /dev/ceph-b432de26-c075-4097-b699-1cf0f41f7402/osd-block-b432de26-c075-4097-b699-1cf0f41f7402 * vgremove -v ceph-b432de26-c075-4097-b699-1cf0f41f7402 * pvremove -v /dev/mapper/crypt-b432de26-c075-4097-b699-1cf0f41f7402 * cryptsetup close /dev/mapper/crypt-b432de26-c075-4097-b699-1cf0f41f7402 * partprobe /dev/nvme6n1
The last step was just to make sure that all was fine.
So I would be great if the addition of a disk fails due e.g. a problem with the bluestore, the whole creation of the lvm, vg, pv & crypto device would be reversed.
Hi Alex,
The step I took as 'juju add-disk ceph-osd devices= '/dev/nvme6p1' . This step failed as there was no room in the bluestore to add another db & wal lvm.
This made the disk /dev/nvme6p1 unusable and to get is back to a state in where I could re-add it to the charm, I had to take the following actions:
* lvremove -v /dev/ceph- b432de26- c075-4097- b699-1cf0f41f74 02/osd- block-b432de26- c075-4097- b699-1cf0f41f74 02 c075-4097- b699-1cf0f41f74 02 crypt-b432de26- c075-4097- b699-1cf0f41f74 02 crypt-b432de26- c075-4097- b699-1cf0f41f74 02
* vgremove -v ceph-b432de26-
* pvremove -v /dev/mapper/
* cryptsetup close /dev/mapper/
* partprobe /dev/nvme6n1
The last step was just to make sure that all was fine.
So I would be great if the addition of a disk fails due e.g. a problem with the bluestore, the whole creation of the lvm, vg, pv & crypto device would be reversed.