From: Greg Farnum <gregory.farnum@dreamhost.com>
To: Damien Churchill <damoxc@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: pgs stuck inactive
Date: Wed, 18 Apr 2012 11:41:37 -0700 [thread overview]
Message-ID: <D4642C5210F144238EA7E60F317364ED@dreamhost.com> (raw)
In-Reply-To: <CAFtEh-d42ch4Oub1ArNcZd5=EYxPejRb0+N2ND4H2o5VaTpCfQ@mail.gmail.com>
On Tuesday, April 17, 2012 at 11:41 PM, Damien Churchill wrote:
> On 17 April 2012 17:49, Greg Farnum <gregory.farnum@dreamhost.com (mailto:gregory.farnum@dreamhost.com)> wrote:
> > Do you know what version this was created with, and what upgrades you've been through? My best guess right now is that there's a problem with the encoding and decoding that I'm going to have to track down, and more context will make it a lot easier. :)
>
>
>
> Hmmm that's testing my memory, I'd say that cluster has been alive at
> least since 0.34. Occasionally I think there was a version skipped,
> not sure if that could cause any issues?
Okay. So the good news is that we can see what's broken now and have a kludge to prevent it happening to others; the bad news is we still have no idea how it actually occurred. :( But I don't think it's worth investing the time given what we have available, so all we can do is repair your cluster.
Are you building your binaries from source, and can you run a patched version of the monitors? If you can I'll give you a patch to enable a simple command that should make things work; otherwise we'll need to start editing things by hand. (Yucky)
-Greg
next prev parent reply other threads:[~2012-04-18 18:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 8:12 pgs stuck inactive Damien Churchill
2012-04-04 20:51 ` Samuel Just
2012-04-04 21:44 ` Damien Churchill
2012-04-06 16:50 ` Samuel Just
2012-04-06 16:55 ` Damien Churchill
2012-04-06 17:30 ` Samuel Just
2012-04-06 17:53 ` Damien Churchill
[not found] ` <CACLRD_3hqoOqbZWnyft3B+pEaPG=pmiDt5HeQASUC=OPS-uA7Q@mail.gmail.com>
[not found] ` <CAFtEh-dnR0zu=ct-gG0L+76BTYHVFimjFKNhHjnDNZWA=Scs1g@mail.gmail.com>
2012-04-06 18:20 ` Samuel Just
[not found] ` <CAFtEh-cx2by6yG_xiQbq5e2fbViOWyHoaOLFPBCZgX7x-7gwFA@mail.gmail.com>
[not found] ` <CACLRD_0UrwKJuELiZqrL7Q_5AjB1EvOd5gqLRzrxw_7AFMcjxg@mail.gmail.com>
[not found] ` <CAFtEh-fwt9BwZ7NwZaJVnwq3hgzvkrb1XvKT0uF81vePRcu7oA@mail.gmail.com>
2012-04-10 21:49 ` Samuel Just
2012-04-10 22:03 ` Damien Churchill
2012-04-10 23:00 ` Samuel Just
2012-04-10 23:40 ` Greg Farnum
2012-04-12 15:29 ` Damien Churchill
2012-04-13 19:30 ` Greg Farnum
2012-04-13 19:42 ` Damien Churchill
2012-04-17 0:06 ` Greg Farnum
2012-04-17 5:32 ` Damien Churchill
2012-04-17 16:49 ` Greg Farnum
2012-04-18 4:35 ` Martin Wilderoth
2012-04-18 6:41 ` Damien Churchill
2012-04-18 18:41 ` Greg Farnum [this message]
2012-04-18 19:04 ` Damien Churchill
2012-04-18 20:41 ` Greg Farnum
2012-04-19 9:07 ` Damien Churchill
2012-04-19 17:09 ` Greg Farnum
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=D4642C5210F144238EA7E60F317364ED@dreamhost.com \
--to=gregory.farnum@dreamhost.com \
--cc=ceph-devel@vger.kernel.org \
--cc=damoxc@gmail.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