On 2023/08/02 13:29, Roland Giesler wrote:
On 2023/08/02 12:53, Igor Fedotov wrote:
Roland,
First of all there are no block.db/block.wal symlinks in OSD folder.
Which means there are no standalone DB/WAL any more.
That is surprising. So ceph-volume is not able to extract the DB/WAL
from an OSD to migrate it it seems?
I figured out the if one doesn't specify and separate LV for the DB/WAL,
it is integrated into the data drive.
However, one can create a new DB/WAL for and OSD as follows:
# systemctl stop ceph-osd@14
# ceph-bluestore-tool bluefs-bdev-new-db --path
/var/lib/ceph/osd/ceph-14 --dev-target
/dev/NodeC-nvme1/NodeC-nvme-LV-RocksDB1 --bluestore-block-db-size 45G
inferring bluefs devices from bluestore path
DB device added /dev/dm-20
# systemctl start ceph-osd@14
And, viola!, it did it.
# ls -la /var/lib/ceph/osd/ceph-14/block*
lrwxrwxrwx 1 ceph ceph 50 Dec 25 2022 /var/lib/ceph/osd/ceph-14/block
-> /dev/mapper/0GVWr9-dQ65-LHcx-y6fD-z7fI-10A9-gVWZkY
lrwxrwxrwx 1 root root 10 Aug 2 21:17
/var/lib/ceph/osd/ceph-14/block.db -> /dev/dm-20
I'm just check it out now, so see if there are no errors and that it
actually does what I think it does.
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
