Hi Florent, It is unusual to manually run the sgdisk. Is there a reason why you need to do this instead of letting ceph-disk prepare do it for you ? The information about the association between journal and data is only displayed when the OSD has been activated. See http://workbench.dachary.org/ceph/ceph/blob/giant/src/ceph-disk#L2246 Cheers On 21/12/2014 15:11, Florent MONTHEL wrote: > Hi, > > I would like to separate OSD and journal on 2 différent disks so I have : > > 1 disk /dev/sde (1GB) for journal => type code JOURNAL_UUID = '45b0969e-9b03-4f30-b4c6-b4b80ceff106' > 1 disk /dev/sdd (5GB) for OSD => type code OSD_UUID = '4fbd7e29-9d25-41b8-afd0-062c0ceff05d' > > I execute below commands : > > FOR JOURNAL : > sgdisk --new=1:0:1023M --change-name="1:ceph journal" --partition-guid=1:e89f18cc-ae46-4573-8bca-3e782d45849c --typecode=1:45b0969e-9b03-4f30-b4c6-b4b80ceff106 -- /dev/sde > > FOR OSD: > sgdisk --new=1:0:5119M --change-name="1:ceph data" --partition-guid=1:7476f0a8-a6cd-4224-b64b-a4834c32a73e --typecode=1:4fbd7e29-9d25-41b8-afd0-062c0ceff05d -- /dev/sdd > > And I'm preparing OSD : > ceph-disk prepare --osd-uuid 7476f0a8-a6cd-4224-b64b-a4834c32a73e --journal-uuid e89f18cc-ae46-4573-8bca-3e782d45849c --fs-type xfs --cluster ceph -- /dev/sdd1 /dev/sde1 > > > After that, I don’t see relation between /dev/sde1 & /dev/sdc1 > > root@falcon:/srv/ceph01adm001/data/cluster-ceph01# ceph-disk list > /dev/sdd : > /dev/sdd1 ceph data, prepared, cluster ceph > /dev/sde : > /dev/sde1 ceph journal > > Is it normal ? > > Thanks > > > *Florent Monthel** > * > > > > > > > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > -- Loïc Dachary, Artisan Logiciel Libre
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com