|
On 05/10/17 22:07, David Turner wrote:
Are you mounting your OSDs using fstab or anything
else? Ceph uses udev rules and partition identifiers to know
what a disk is and where to mount it, assuming that you have
your GUIDs set properly on your disks. ceph-deploy does this by
default.
`update-rc.d 'ceph' defaults 99`
That should put it last in the boot order. The '99'
here is a number 01-99 where the lower the number the
earlier in the boot sequence the service is started. To
see what order your service is set to start and stop, `ls
/etc/rc*.d/*{service}. Each rc# represents the
runlevels. K## is the order that services will be
stopped, S$$ is the order that services will be started.
After you run the above command, it should change Ceph to
S99. If you want to fine tune it, you can see which
services are starting up after ceph and see if you can
locate the specific one that is causing your problems.
I think that might be sys-v specific.
David,
ceph tell osd.12 version replies
version 11.2.0
Distro is Ubuntu 14.04.5 LTS
(trusty) which utilizes upstart for ceph.
I don’t see a good way ensure
last in an event based system like upstart.
But speaking of sys-v... I am using Ubuntu 14.04 with ceph, and I
don't use the upstart stuff. I don't like it, except that it works
great if you just pretend it's sys-v. :)
So to use it like sysv, just do this for mons, osds, etc.:
rm /var/lib/ceph/osd/ceph-.../upstart
touch /var/lib/ceph/osd/ceph-.../sysvinit
And then start it the sys-v way, like:
service ceph start osd.0
Use update-rc.d to change the order. And you can see the order of
the sys-v side of it like: ls -1 /etc/rc2.d/ (where 2 is your
runlevel)
|
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
