From: John Spray <john.spray@redhat.com>
To: Sage Weil <sweil@redhat.com>,
ceph-devel@vger.kernel.org, ceph-calamari@ceph.com
Subject: Re: [ceph-calamari] disk failure prediction
Date: Thu, 19 Feb 2015 08:56:25 +0000 [thread overview]
Message-ID: <54E5A539.1060803@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1502181514400.24259@cobra.newdream.net>
On 18/02/2015 23:20, Sage Weil wrote:
> We wouldn't see
> quite the same results since our "raid sets" are effectively entire pools
I think we could do better than pool-wide, e.g. if multiple drives in
one chassis are at risk (where PG stores at most one copy per chassis),
we can identify that as less severe than the general case where multiple
at-risk drives might be in the same PG. Making it CRUSH-aware like this
would be a good hook for users to take advantage of the ceph/calamari
SMART monitoring rather than rolling their own.
John
next prev parent reply other threads:[~2015-02-19 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 23:20 disk failure prediction Sage Weil
2015-02-19 8:56 ` John Spray [this message]
2015-02-19 14:58 ` [ceph-calamari] " Sage Weil
2015-02-19 15:59 ` 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=54E5A539.1060803@redhat.com \
--to=john.spray@redhat.com \
--cc=ceph-calamari@ceph.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sweil@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox