From: John Spray <john.spray@redhat.com>
To: Mark Nelson <mnelson@redhat.com>,
"Handzik, Joe" <joseph.t.handzik@hp.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Advice for implementation of LED behavior in Ceph ecosystem
Date: Wed, 01 Apr 2015 23:04:31 +0100 [thread overview]
Message-ID: <551C6B6F.9080308@redhat.com> (raw)
In-Reply-To: <551C69B1.9070100@redhat.com>
On 01/04/2015 22:57, Mark Nelson wrote:
> It seems to me that the OSD potentially would flash the LED on it's
> way down if it thinks it's drive is dead/dying?
That's a good idea for the case where ceph-osd is proactively
identifying a failing drive. I'm also thinking about the case where we
come back from a reboot and a drive is sufficiently unreadable that
ceph-disk doesn't see the OSD partitions and ceph-osd never gets
started, or the OSD's local filesystem is unmountable. Because the
keyring lives on that local filesystem, OSDs couldn't phone home in that
case, even to report a failure.
John
next prev parent reply other threads:[~2015-04-01 22:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 18:56 Advice for implementation of LED behavior in Ceph ecosystem Handzik, Joe
2015-04-01 20:27 ` Mark Nelson
2015-04-01 20:29 ` Sage Weil
2015-04-01 21:17 ` John Spray
2015-04-01 21:55 ` John Spray
2015-04-01 21:57 ` Mark Nelson
2015-04-01 22:04 ` John Spray [this message]
2015-04-01 22:06 ` Mark Nelson
2015-04-01 22:07 ` John Spray
2015-04-01 22:10 ` Handzik, Joe
2015-04-01 23:17 ` Sage Weil
2015-04-01 23:48 ` Handzik, Joe
[not found] <2C438B34CAC8264398F5C7AF7411910A6341F7BD@G4W3206.americas.hpqcorp.net>
[not found] ` <61596DF5-5893-4F29-B3A3-DC2CEBDCD119@redhat.com>
2015-04-21 14:46 ` Gregory Meno
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=551C6B6F.9080308@redhat.com \
--to=john.spray@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=joseph.t.handzik@hp.com \
--cc=mnelson@redhat.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.