Thank you Alfredo. I now got it.
On 2013-11-19 20:44, Alfredo Deza wrote:
That really doesn't restart them, it creates them. I think ceph-deploy
is not destroying anything
here so it appears like it restarts when in fact is re-doing the whole
process again.
_
On 11/19/13, 1:29 AM, "Dnsbed Ops" wrote:
>Hi,
>
>When an osd node server restarted, I found the osd daemon doesn't get
>started.
>
>I must run these two commands from the deploy node to restart them:
>
>ceph-deploy osd prepare ceph3.anycast.net:/tmp/osd2
>ceph-deploy osd activate ceph3.anycast.n
On Tue, Nov 19, 2013 at 1:29 AM, Dnsbed Ops wrote:
> Hi,
>
> When an osd node server restarted, I found the osd daemon doesn't get
> started.
>
> I must run these two commands from the deploy node to restart them:
>
> ceph-deploy osd prepare ceph3.anycast.net:/tmp/osd2
> ceph-deploy osd activate c
Hi,
When an osd node server restarted, I found the osd daemon doesn't get
started.
I must run these two commands from the deploy node to restart them:
ceph-deploy osd prepare ceph3.anycast.net:/tmp/osd2
ceph-deploy osd activate ceph3.anycast.net:/tmp/osd2
My questions are,
#1, can it be set
