All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Spray <jspray@redhat.com>
To: Wyllys Ingersoll <wyllys.ingersoll@keepertech.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: ceph osd metadata fails if any osd is down
Date: Wed, 21 Sep 2016 22:12:40 +0100	[thread overview]
Message-ID: <CALe9h7dR7oqP73JfBHHFwQYK8TkhRVM2fKtvCi4YoZEk4s4Z8g@mail.gmail.com> (raw)
In-Reply-To: <CAGbviv+8SkMApa8sbc4-ZjvRxRUVM-SZR+dt2u1CvGshVRoinA@mail.gmail.com>

On Wed, Sep 21, 2016 at 6:29 PM, Wyllys Ingersoll
<wyllys.ingersoll@keepertech.com> wrote:
> In 10.2.2 when running "ceph osd metadata" (defaulting to get metdata for
> "all" OSDs), if even 1 OSD is currently marked "down", the entire command
> fails and returns an error:
>
> $ ceph osd metadata
> Error ENOENT:
>
> - One OSD in the cluster was "down", I removed that OSD and re-ran the
> command successfully.
>
> It seems that the "metadata" command should be able to dump the data for
> the OSDs that are up and ignore the ones that are down.  Is this a known
> bug?

Probably fixed by
https://github.com/ceph/ceph/commit/f5db5a4b0bb52fed544f277c28ab5088d1c3fc79
which is in 10.2.3

John

>
> -Wyllys Ingersoll
>  Keeper Technology, LLC
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-09-21 21:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 17:29 ceph osd metadata fails if any osd is down Wyllys Ingersoll
2016-09-21 21:12 ` John Spray [this message]
2016-10-24 16:35   ` Wyllys Ingersoll
2016-10-24 17:17     ` Sage Weil
2016-10-24 17:25       ` Wyllys Ingersoll
2016-10-25 12:36         ` kefu chai

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=CALe9h7dR7oqP73JfBHHFwQYK8TkhRVM2fKtvCi4YoZEk4s4Z8g@mail.gmail.com \
    --to=jspray@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=wyllys.ingersoll@keepertech.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.