Re: Process for adding a separate block.db to an osd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Eugene,

Thanks for your help. The info is rea/usr/bin/ceph --cluster ceph --name client.osd-lockbox.${OSD_FSID} --keyring $OSD_PATH/lockbox.keyring config-key get dm-crypt/osd/$OSD_FSID/lukslly helpful. In my case, the OSDs were encrypted so the process is a bit more involved but I managed to get them all separated. 

--TH


September 19, 2020 2:08 AM, "Eugen Block" <eblock@xxxxxx> wrote:

> Don’t forget to change the lv tags and make sure ceph-bluestore-tool 
> show-label has the right labels. This has been discussed multiple 
> times [1].
> 
> [1] 
> https://lists.ceph.io/hyperkitty/list/ceph-users@xxxxxxx/thread/GSFUUIMYDPSFM2HHO25TCTPLTXBS3O2K
> 
> Zitat von tri@xxxxxxxxxx:
> 
>> Hey all,
>> 
>> I'm trying to figure out the appropriate process for adding a
>> separate SSD block.db to an existing OSD. From what I gather the two
>> steps are:
>> 
>> 1. Use ceph-bluestore-tool bluefs-bdev-new-db to add the new db device
>> 2. Migrate the data ceph-bluestore-tool bluefs-bdev-migrate
>> 
>> I followed this and got both executed fine without any error. Yet
>> when the OSD got started up, it keeps on using the integrated
>> block.db instead of the new db. The block.db link to the new db
>> device was deleted. Again, no error, just not using the new db
>> 
>> Any suggestion? Thanks.
>> 
>> --Tri Hoang
>> 
>> root@elmo:/#CEPH_ARGS="--bluestore_block_db_size=26843545600
>> --bluestore_block_db_create=true" ceph-bluestore-tool --path
>> /mnt/ceph/c258000c-f3e4-11ea-9ebe-c3c75e8e9028/osd.2
>> bluefs-bdev-new-db --dev-target /dev/vg/sdc.db
>> inferring bluefs devices from bluestore path
>> DB device added /dev/dm-8
>> 
>> root@elmo:/# ceph-bluestore-tool --path
>> /mnt/ceph/c258000c-f3e4-11ea-9ebe-c3c75e8e9028/osd.2 --devs-source
>> /mnt/ceph/c258000c-f3e4-11ea-9ebe-c3c75e8e9028/osd.2/block
>> --dev-target
>> /mnt/ceph/c258000c-f3e4-11ea-9ebe-c3c75e8e9028/osd.2/block.db
>> bluefs-bdev-migrate
>> inferring bluefs devices from bluestore path
>> _______________________________________________
>> ceph-users mailing list -- ceph-users@xxxxxxx
>> To unsubscribe send an email to ceph-users-leave@xxxxxxx
> 
> _______________________________________________
> ceph-users mailing list -- ceph-users@xxxxxxx
> To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux