From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Sylvain Munaut <s.munaut@whatever-company.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: ceph gets stopped but never started...
Date: Thu, 30 May 2013 15:01:19 +0200 [thread overview]
Message-ID: <51A74D9F.7000206@profihost.ag> (raw)
In-Reply-To: <CAF6-1L70z8xpZVQtDXJj4h+SY7TxrN2rAz-OAR-BXkJR_4DjxQ@mail.gmail.com>
Am 30.05.2013 14:57, schrieb Sylvain Munaut:
> Hi
>
>> since commit 85fb422a084785176af3b694882964841e02195d in cuttle fish
>> cherry-picked from 2f193fb931ed09d921e6fa5a985ab87aa4874589 ceph gets
>> stopped on debian while upgrading but it never gets started again??
>>
>> Does this really makes sense?
>>
>> Should the admin handle the stop / start / restart on upgrade?
>
> Yes, personally I think so.
>
> I mean , I usually restart osd sequentially "by hand" while the
> upgrade is usually done cluster wide by some automation but for the
> service to stay up, the restart needs to be handled manually.
Same for me.
Stefan
next prev parent reply other threads:[~2013-05-30 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 11:30 ceph gets stopped but never started Stefan Priebe - Profihost AG
2013-05-30 12:57 ` Sylvain Munaut
2013-05-30 13:01 ` Stefan Priebe - Profihost AG [this message]
2013-05-30 15:46 ` Sage Weil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51A74D9F.7000206@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=s.munaut@whatever-company.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.