Robert,
thanks a lot for the feedback!
I was very worried about the same thing! Glad to know tha Ceph's
automagic takes care of everything :-P
Best regards,
George
If you use ceph-disk (and I believe ceph-depoly) to create your OSDs,
or you go through the manual steps to set up the
Hi Robert,
just to make sure I got it correctly:
Do you mean that the /etc/mtab entries are completely ignored and no
matter what the order
of the /dev/sdX device is Ceph will just mount correctly the osd/ceph-X
by default?
In addition, assuming that an OSD node fails for a reason other
If you use ceph-disk (and I believe ceph-depoly) to create your OSDs, or
you go through the manual steps to set up the partition UUIDs, then yes
udev and the init script will do all the magic. Your disks can be moved to
another box without problems. I've moved disks to different ports on
I have not used ceph-deploy, but it should use ceph-disk for the OSD
preparation. Ceph-disk creates GPT partitions with specific partition
UUIDS for data and journals. When udev or init starts the OSD, or mounts it
to a temp location reads the whoami file and the journal, then remounts it
in the
Indeed it is not necessary to have any OSD entries in the Ceph.conf
file
but what happens in the event of a disk failure resulting in changing
the mount device?
For what I can see is that OSDs are mounted from entries in /etc/mtab
(I am on CentOS 6.6)
like this:
/dev/sdj1
Hi teqm,
Is it necessary to indicate in ceph.conf all OSD that we have in the
cluster ?
we have today reboot a cluster (5 nodes RHEL 6.5) and some OSD seem to have
change ID so crush map not mapped with the reality
Thanks
*Florent Monthel*
___
