@Alfredo - Is this something that ceph-deploy should do // or warn about? or should we fix ceph-disk so that it set's the part guid on existing partations?
On Mon, Dec 9, 2013 at 9:44 AM, Matthew Walster <[email protected]> wrote: > On 9 December 2013 17:35, Andrew Woodward <[email protected]> wrote: > >> https://github.com/ceph/ceph/blob/master/udev/95-ceph-osd.rules Lists >> the 4 variants, in your case it sounds like a normal ceph volume so the >> guid you want is probably 4fbd7e29-9d25-41b8-afd0-062c0ceff05d. >> >> You will need sgdisk to set the guid correctly (part of gdisk) >> >> from man >> -t, --typecode=partnum:{hexcode|GUID} >> Change a single partition's type code. You enter the type >> code >> using either a two-byte hexadecimal number, as described >> earβ >> lier, or a fully-specified GUID value, such >> as >> EBD0A0A2-B9E5-4433-87C0-68B6B72699C7. >> >> your exec should look like >> >> sgdisk --typecode=4:4fbd7e29-9d25-41b8-afd0-062c0ceff05d /dev/sda >> β >> > > Wow! That's well hidden! > > I've only had a cursory look at ceph-deploy's underlying code -- is this a > feature missing from there, or is there a reason it's left out of the "osd > prepare" phase? > > It would be good to either document this on the ceph-deploy quickstart > page or incorporate it into ceph-deploy. I can confirm sgdisk is in the > path on login. > > Matthew > > ββ > -- If google has done it, Google did it right!
_______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
