Dan, It is not necessary to specify the OSD data in ceph.conf anymore. Ceph has two auto-start functions besides this method.
udev rules: ceph uses a udev rule to scan and attempt to mount (and activate) partitions with specific GUID set for the partition typecode > sgdisk --typecode=<<partation number>>:<<GUID>> /dev/<<disk>> the exact GUID's to use can be found https://github.com/ceph/ceph/blob/master/udev/95-ceph-osd.rules. These are set automaticly using ceph-disk (or ceph-deploy) if it creates the partition from an empty disk, in the case that it does not, you have to set them by hand, all be it should probably do this, or at least tell you should do this. ceph init script: the ceph init script will scan /var/lib/ceph/osd (or the otherwise configured location) for <cluster name>-<id> (default cluster name is ceph) folders and attempt to start the osd service for each of them if they look correct lastly, and possibly the most annoying way is that you can configure each OSD and path in ceph.conf, I don't have any good examples as the two prior are more flexible / require less config. On Fri, Aug 8, 2014 at 8:53 AM, O'Reilly, Dan <[email protected]> wrote: > Does anybody have a good sample ceph.conf file I can use for reference? > I’m having a problem where OSD’s won’t come back up after a sysem reboot. > > > > Dan O'Reilly > > UNIX Systems Administration > > [image: cid:638154011@09122011-048B] > > 9601 S. Meridian Blvd. > > Englewood, CO 80112 > > 720-514-6293 > > > > > > _______________________________________________ > Ceph-community mailing list > [email protected] > http://lists.ceph.com/listinfo.cgi/ceph-community-ceph.com > > -- Andrew Mirantis Ceph community
_______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
