Re: Help with osd spec needed

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

 



Hi,

if you assigned the SSD to be for block.db it won't be available from the orchestrator's point of view as a data device. What you could try is to manually create a partition or LV on the remaining SSD space and then point the service spec to that partition/LV via path spec. I haven't tried that myself though, so I have no clue if that'll work.

Regards,
Eugen

Zitat von Kristaps Cudars <kristaps.cudars@xxxxxxxxx>:

3 nodes each:
3 hdd – 21G
1 ssd – 80G

Create osd containing block_data with block_db size 15G located on ssd-
This par works
Create block_data osd on remaining space 35G in ssd- This part is not
working

ceph orch apply osd -i /path/to/osd_spec.yml

service_type: osd
service_id: osd_spec_hdd
placement:
  host_pattern: '*'
spec:
  block_db_size: 15G
  db_slots: 3
  data_devices:
    rotational: 1
  db_devices:
    rotational: 0
---
service_type: osd
service_id: odd_spec_ssd
placement:
  host_pattern: '*'
spec:
  data_devices:
    rotational: 0
_______________________________________________
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