|
hmm, helps partially ... running
/usr/sbin/ceph-disk trigger /dev/sdc1 or sdb1 works and brings
osd up..
systemctl enable does not help....
Am 11.07.2016 um 14:49 schrieb George
Shuklin:
Short story how OSDs are started in
systemd environments:
Ceph OSD parittions has specific typecode (partition type 4FBD7E29-9D25-41B8-AFD0-062C0CEFF05D).
It handled by udev rules shipped by ceph package:
/lib/udev/rules.d/95-ceph-osd.rules
It set up proper owner/group for this disk ('ceph' instead
'root') and calls /usr/sbin/ceph-disk trigger.
ceph-disk triggers creation of instance of ceph-disk@ systemd
unit (to mount disk to /var/lib/ceph/osd/...), and ceph-osd@
(i'm not sure about all sequence of events).
Basically, to make OSD autostart they NEED to have proper
typecode in their partition. If you using something different
(like 'directory based OSD') you should enable OSD autostart:
systemctl enable ceph-osd@42
On 07/11/2016 03:32 PM, Dirk Laurenz wrote:
Hello,
i'm new to ceph an try to do some first steps with ceph to
understand concepts.
my setup is at first completly in vm....
i deployed (with ceph-deploy) three monitors and three osd
hosts. (3+3 vms)
my frist test was to find out, if everything comes back online
after a system restart. this works fine for the monitors, but
fails for the osds. i have to start them manually.
OS is debian jessie, ceph is the current release....
Where can find out, what's going wrong....
Dirk
_______________________________________________
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
|
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
