On 03/19/2015 12:27 PM, Robert LeBlanc wrote: > Udev already provides some of this for you. Look in /dev/disk/by-*. > You can reference drives by UUID, id or path (for > SAS/SCSI/FC/iSCSI/etc) which will provide some consistency across > reboots and hardware changes. Thanks for the quick responses. And to Kobi (off list) as well. It seems the optimal way to do this is to create the OSDs by ID in the first place. So, for /dev/sde with a journal on /dev/sda5: root@osd1:~$ ls -l /dev/disk/by-id/ | grep sde lrwxrwxrwx 1 root root 9 Mar 19 23:36 ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E5TUCJX9 -> ../../sde lrwxrwxrwx 1 root root 9 Mar 19 23:36 wwn-0x50014ee20a66aefe -> ../../sde root@osd1:~$ ls -l /dev/disk/by-id/ | grep sda5 lrwxrwxrwx 1 root root 10 Mar 19 23:36 ata-Crucial_CT480M500SSD1_14210C292B50-part5 -> ../../sda5 lrwxrwxrwx 1 root root 10 Mar 19 23:36 wwn-0x500a07510c292b50-part5 -> ../../sda5 The deploy command looks like this: ceph-deploy --overwrite-conf osd create osd1:/dev/disk/by-id/wwn-0x50014ee20a66aefe:/dev/disk/by-id/wwn-0x500a07510c292b50-part5 And alternatively, create a udev rule set for existing devices. I haven't tested yet, but I am guessing that the udev rule for that same disk (deployed as sde) would look something like this: KERNEL=="sde", SUBSYSTEM=="block", DEVLINKS=="/dev/disk/by-id/wwn-0x50014ee20a66aefe" Many thanks for the assistance! Colin _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |