From: "Jim Schutt" <jaschut@sandia.gov>
To: Samuel Just <sam.just@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: osd/OSDMap.h: 330: FAILED assert(is_up(osd))
Date: Tue, 17 Jul 2012 15:54:04 -0600 [thread overview]
Message-ID: <5005DEFC.7020701@sandia.gov> (raw)
In-Reply-To: <CA+4uBUZ1j6dx3Z68_BG=eS+nas+mf75Dqf9qV+-0C_UFC=oDAA@mail.gmail.com>
On 07/17/2012 03:44 PM, Samuel Just wrote:
> Not quite. OSDService::get_osdmap() returns the most recently
> published osdmap. Generally, OSD::osdmap is safe to use when you are
> holding the osd lock. Otherwise, OSDService::get_osdmap() should be
> used. There are a few other things that should be fixed surrounding
> this issue as well, I'll put some time into it today. The map_lock
> should probably be removed all together.
Thanks for taking a look. Let me know when
you get something, and I'll take it for a spin.
Thanks -- Jim
> -Sam
next prev parent reply other threads:[~2012-07-17 21:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 20:49 osd/OSDMap.h: 330: FAILED assert(is_up(osd)) Jim Schutt
2012-07-17 21:44 ` Samuel Just
2012-07-17 21:54 ` Jim Schutt [this message]
2012-07-18 0:03 ` Samuel Just
2012-07-18 15:29 ` Jim Schutt
2012-07-18 18:03 ` Samuel Just
2012-07-18 18:42 ` Jim Schutt
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=5005DEFC.7020701@sandia.gov \
--to=jaschut@sandia.gov \
--cc=ceph-devel@vger.kernel.org \
--cc=sam.just@inktank.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.