My inquiry may be a fundamental Linux thing and/or requiring basic Ceph guidance. According to the CBT ReadMe -- https://github.com/ceph/cbt ------------ Currently CBT looks for specific partition labels in /dev/disk/by-partlabel for the Ceph OSD data and journal partitions. ...each OSD host partitions should be specified with the following gpt labels: osd-device-<num>-data osd-device-<num>-journal ------------ Does this mean that a disk formatted with fdisk in MBR/DOS format style should be changed to GPT? I've been taking some advice from peers directing use of fdisk. What is recommended disk prep tool and partition format (GPT/MBR)? Or should I be using ceph-disk exclusively? (and be done with it! <grin>) Also on the CBT ReadMe is a script that Users are encouraged to inspect: mkpartmagna.sh https://github.com/ceph/cbt/blob/master/tools/mkpartmagna.sh The core task is iterating over items in directory /dev/disk/by-id. ==> However, my /dev/disk/by-id is not populated with items. <== I realize this is a Linux thing... however I am not familiar with it. When I google the topic I appears to be called persistent block device naming. Does the parted command create the necessary labels that CBT requires? Is there an extra step required to make the labels appear in /dev/disk/by-id Are the Ceph udev rules related to this disk by-id naming? And finally, are the Ceph udev rules a requirement for a proper installation of Ceph? And if you read this far... bonus question. :) In this parted command, parted -s -a optimal /dev/$DEV mkpart osd-device-$i-data $sp% $ep%" What function/feature do the variables $sp and $ep, hold for us? Or what may have been the author's intent? BTW, although cross--posted, I tried to set a reply-to for CBT list only. We see how it goes. Thanks in advance. -az _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |