Re: 2 OSD's per drive , unable to start the osd's

["sandeep.coolboy@xxxxxxxxx" <sandeep.coolboy@xxxxxxxxx>]

Hi Burkhard,

How can i achieve that so all the OSD's will auto start at boot time? 

Regards,

Sandeep

On Fri, Dec 16, 2016 at 2:39 PM, Burkhard Linke <Burkhard.Linke@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi,

On 12/16/2016 09:22 AM, sandeep.coolboy@xxxxxxxxx wrote:

Hi,

I was trying the scenario where i have partitioned my drive (/dev/sdb) into 4 (sdb1, sdb2 , sdb3, sdb4) using the sgdisk utility:

# sgdisk -z /dev/sdb

# sgdisk -n 1:0:+1024 /dev/sdb -c 1:"ceph journal"

# sgdisk -n 1:0:+1024 /dev/sdb -c 2:"ceph journal"

# sgdisk -n 1:0:+4096 /dev/sdb -c 3:"ceph data"

# sgdisk -n 1:0:+4096 /dev/sdb -c 3:"ceph data"

checked the partition with lsblk and it has created the partitions as expected.

im using the ceph-disk command to create the osd's:

# ceph-disk prepare --cluster ceph /dev/sdb3 /dev/sdb1

prepare_device: OSD will not be hot-swappable if journal is not the same device as the osd data
prepare_device: Journal /dev/sdb1 was not prepared with ceph-disk. Symlinking directly.
set_data_partition: incorrect partition UUID: 0fc63daf-8483-4772-8e79-3d69d8477de4, expected ['4fbd7e29-9d25-41b8-afd0-5ec00ceff05d', '4fbd7e29-9d25-41b8-afd0-062c0ceff05d', '4fbd7e29-8ae0-4982-bf9d-5a8d867af560', '4fbd7e29-9d25-41b8-afd0-35865ceff05d']

*snipsnap*

CEPH OSD and journal partitions have a certain partition type UUID, as the message suggests. To avoid problems with OSD autodetection at boot time you need to change the UUID.

Regards,
Burkhard

_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com