One thing than can cause this is messed-up partition ID's / typecodes. Check
out the ceph-disk script to see how they get applied. I have a few systems
that somehow got messed up -- at boot they don't get started, but if I mounted
them manually on /mnt, checked out the whoami file and remoun
I'm running Ubuntu 14.04 servers with Firefly and I don't have a sysvinit
file, but I do have an upstart file.
"touch /var/lib/ceph/osd/ceph-XX/upstart" should be all you need to do.
That way, the OSD's should be mounted automatically on boot.
On 30 January 2015 at 10:25, Alexis KOALLA wrote:
>
Hi Lindsay and Daniel
Thanks for your replies.
Apologize for not specifying my LAB env details :
Here is the details:
OS: Ubuntu 14.04 LTS, Kernel 3.8.0-29-generic
Ceph version: Firefly 0.80.8
env: LAB
@Lindsay : I'm wonderring if putting the mount command in fstab is new
to ceph or it is recom
On 29/01/15 15:05, Alexis KOALLA wrote:
> Issue: The servers that host the OSDs have rebooted and we have observed
> that after the reboot there is no auto mount of OSD devices and we need
> to manually performed the mount and then start the OSD as below:
>
> 1- [root@osd.0] mount /dev/sdb2 /var/l
On Thu, 29 Jan 2015 03:05:41 PM Alexis KOALLA wrote:
> Hi,
> Today we encountered an issue in our Ceph cluster in LAB.
> Issue: The servers that host the OSDs have rebooted and we have observed
> that after the reboot there is no auto mount of OSD devices and we need
> to manually performed th
Hi,
Today we encountered an issue in our Ceph cluster in LAB.
Issue: The servers that host the OSDs have rebooted and we have observed
that after the reboot there is no auto mount of OSD devices and we need
to manually performed the mount and then start the OSD as below:
1- [root@osd.0] mou
