I came across this a few times. My problem was with journals I set up by myself. I didn't give them the proper GUID partition type ID so the udev rules didn't know how to make sure the partition looked correct. What the udev rules were unable to do was chown the journal block device as ceph:ceph so that it could be opened by the Ceph user. You can test by chowning the journal block device and try to start the OSD again.
Alternatively if you want to see more information, you can start the daemon manually as opposed to starting it through systemd and see what its output looks like. On Tue, Jun 13, 2017 at 6:32 AM nokia ceph <nokiacephus...@gmail.com> wrote: > Hello, > > Some osd's not getting activated after a reboot operation which cause that > particular osd's landing in failed state. > > Here you can see mount points were not getting updated to osd-num and > mounted as a incorrect mount point, which caused osd.<num> can't able to > mount/activate the osd's. > > Env:- RHEL 7.2 - EC 4+1, v11.2.0 bluestore. > > #grep mnt proc/mounts > /dev/sdh1 /var/lib/ceph/tmp/mnt.om4Lbq xfs > rw,noatime,attr2,inode64,sunit=512,swidth=512,noquota 0 0 > /dev/sdh1 /var/lib/ceph/tmp/mnt.EayTmL xfs > rw,noatime,attr2,inode64,sunit=512,swidth=512,noquota 0 0 > > From /var/log/messages.. > > -- > May 26 15:39:58 cn1 systemd: Starting Ceph disk activation: /dev/sdh2... > May 26 15:39:58 cn1 systemd: Starting Ceph disk activation: /dev/sdh1... > > > May 26 15:39:58 cn1 systemd: *start request repeated too quickly for* > ceph-disk@dev-sdh2.service => suspecting this could be root cause. > May 26 15:39:58 cn1 systemd: Failed to start Ceph disk activation: > /dev/sdh2. > May 26 15:39:58 cn1 systemd: Unit ceph-disk@dev-sdh2.service entered > failed state. > May 26 15:39:58 cn1 systemd: ceph-disk@dev-sdh2.service failed. > May 26 15:39:58 cn1 systemd: start request repeated too quickly for > ceph-disk@dev-sdh1.service > May 26 15:39:58 cn1 systemd: Failed to start Ceph disk activation: > /dev/sdh1. > May 26 15:39:58 cn1 systemd: Unit ceph-disk@dev-sdh1.service entered > failed state. > May 26 15:39:58 cn1 systemd: ceph-disk@dev-sdh1.service failed. > -- > > But this issue will occur intermittently after a reboot operation. > > Note;- We haven't face this problem in Jewel. > > Awaiting for comments. > > Thanks > Jayaram > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
