* Minor inconsistency with ceph-deploy on Giant
@ 2015-02-02 15:19 Stephen Hindle
2015-02-02 15:43 ` Sage Weil
0 siblings, 1 reply; 2+ messages in thread
From: Stephen Hindle @ 2015-02-02 15:19 UTC (permalink / raw)
To: ceph-devel
Hi!
Just thought I'd mention a minor inconsistency I noticed while
re-installing our cluster...
preparing an OSD with ceph-deploy will NOT activate it on a parttion
(node1:/sda1/sda2)
preparting an OSD with ceph-deploy WILL activate it on a disk (
node1:/dev/sdc)
I think I noticed similiar behavior with ceph-deploy osd create, but I
assumed I just messed up,
so I didnt document it. This is probably more of an 'issue' as create is
supposed to activate it for you.
Manually issuing a ceph-deploy osd activate works fine to bring the
partition OSDs up.
--
The information in this message may be confidential. It is intended solely
for
the addressee(s). If you are not the intended recipient, any disclosure,
copying or distribution of the message, or any action or omission taken by
you
in reliance on it, is prohibited and may be unlawful. Please immediately
contact the sender if you have received this message in error.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Minor inconsistency with ceph-deploy on Giant
2015-02-02 15:19 Minor inconsistency with ceph-deploy on Giant Stephen Hindle
@ 2015-02-02 15:43 ` Sage Weil
0 siblings, 0 replies; 2+ messages in thread
From: Sage Weil @ 2015-02-02 15:43 UTC (permalink / raw)
To: Stephen Hindle; +Cc: ceph-devel
On Mon, 2 Feb 2015, Stephen Hindle wrote:
> Hi!
>
> Just thought I'd mention a minor inconsistency I noticed while
> re-installing our cluster...
> preparing an OSD with ceph-deploy will NOT activate it on a parttion
> (node1:/sda1/sda2)
> preparting an OSD with ceph-deploy WILL activate it on a disk (
> node1:/dev/sdc)
>
> I think I noticed similiar behavior with ceph-deploy osd create, but I
> assumed I just messed up,
> so I didnt document it. This is probably more of an 'issue' as create is
> supposed to activate it for you.
>
> Manually issuing a ceph-deploy osd activate works fine to bring the
> partition OSDs up.
This is an artifact of how activation works: we label GPT partitions so
that udev can launch ceph-osd. If you use existing partitions, they
aren't GPT (probably) and aren't labeled accordingly.
I think the "fix" is to make sure the existing partitions are GPT
partitions, and make sure that ceph-disk will relabel is possible (I
forget if it does this now...)
sage
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-02-02 15:43 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-02 15:19 Minor inconsistency with ceph-deploy on Giant Stephen Hindle
2015-02-02 15:43 ` Sage Weil
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.