All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Just <sjust@redhat.com>
To: Sugang Li <sugangli@winlab.rutgers.edu>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: replicatedPG assert fails
Date: Thu, 21 Jul 2016 07:54:02 -0700	[thread overview]
Message-ID: <CAN=+7FWkeX+5zwzuYcHE35ZSHWO7ZyUVG0vHd3Y+K5AEPPsb1w@mail.gmail.com> (raw)
In-Reply-To: <CAG0LsznhUpP=ub-TmiHSO0A9JZWjk8eov2Lu8y15snqcdG_4Aw@mail.gmail.com>

Hmm.  Can you provide more information about the poison op?  If you
can reproduce with
debug osd = 20
debug filestore = 20
debug ms = 1
it should be easier to work out what is going on.
-Sam

On Thu, Jul 21, 2016 at 7:13 AM, Sugang Li <sugangli@winlab.rutgers.edu> wrote:
> Hi all,
>
> I am working on a research project which requires multiple write
> operations for the same object at the same time from the client. At
> the OSD side, I got this error:
> osd/ReplicatedPG.cc: In function 'int
> ReplicatedPG::find_object_context(const hobject_t&, ObjectContextRef*,
> bool, bool, hobject_t*)' thread 7f0586193700 time 2016-07-21
> 14:02:04.218448
> osd/ReplicatedPG.cc: 9041: FAILED assert(oid.pool ==
> static_cast<int64_t>(info.pgid.pool()))
>  ceph version 10.2.0-2562-g0793a28 (0793a2844baa38f6bcc5c1724a1ceb9f8f1bbd9c)
>  1: (ceph::__ceph_assert_fail(char const*, char const*, int, char
> const*)+0x8b) [0x7f059fe6dd7b]
>  2: (ReplicatedPG::find_object_context(hobject_t const&,
> std::shared_ptr<ObjectContext>*, bool, bool, hobject_t*)+0x1dbb)
> [0x7f059f9296fb]
>  3: (ReplicatedPG::do_op(std::shared_ptr<OpRequest>&)+0x186e) [0x7f059f959d7e]
>  4: (ReplicatedPG::do_request(std::shared_ptr<OpRequest>&,
> ThreadPool::TPHandle&)+0x73c) [0x7f059f916a0c]
>  5: (OSD::dequeue_op(boost::intrusive_ptr<PG>,
> std::shared_ptr<OpRequest>, ThreadPool::TPHandle&)+0x3f5)
> [0x7f059f7ced65]
>  6: (PGQueueable::RunVis::operator()(std::shared_ptr<OpRequest>
> const&)+0x5d) [0x7f059f7cef8d]
>  7: (OSD::ShardedOpWQ::_process(unsigned int,
> ceph::heartbeat_handle_d*)+0x86c) [0x7f059f7f003c]
>  8: (ShardedThreadPool::shardedthreadpool_worker(unsigned int)+0x947)
> [0x7f059fe5e007]
>  9: (ShardedThreadPool::WorkThreadSharded::entry()+0x10) [0x7f059fe60160]
>  10: (()+0x8184) [0x7f059e2d2184]
>  11: (clone()+0x6d) [0x7f059c1e337d]
>
> And at the client side, I got segmentation fault.
>
> I am wondering what will be the possible reason that cause the assert fail?
>
> Thanks,
>
> Sugang
> --
> 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-07-21 14:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21 14:13 replicatedPG assert fails Sugang Li
2016-07-21 14:54 ` Samuel Just [this message]
2016-07-21 15:21   ` Sugang Li
2016-07-21 15:22     ` Samuel Just
2016-07-21 15:34       ` Sugang Li
2016-07-21 15:43         ` Samuel Just
2016-07-21 15:47           ` Samuel Just
2016-07-21 15:49             ` Sugang Li
2016-07-21 16:03               ` Samuel Just
2016-07-21 18:11                 ` Sugang Li
2016-07-21 19:28                   ` Samuel Just
2016-07-21 19:36                     ` Sugang Li
2016-07-21 21:59                       ` Samuel Just
2016-07-22 14:00                         ` Sugang Li
2016-07-22 15:27                           ` Samuel Just
2016-07-22 15:30                             ` Sugang Li
2016-07-22 15:36                               ` Samuel Just
2016-07-22 17:07                                 ` Sugang Li
2016-07-22 17:35                                   ` Samuel Just
2016-07-22 18:13                                     ` Sugang Li
2016-07-22 18:31                                       ` Samuel Just
2016-07-22 19:19                                         ` Sugang Li
2016-07-22 19:34                                           ` Samuel Just
2016-07-22 20:53                                             ` Sugang Li
2016-07-22 21:21                                               ` Samuel Just

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='CAN=+7FWkeX+5zwzuYcHE35ZSHWO7ZyUVG0vHd3Y+K5AEPPsb1w@mail.gmail.com' \
    --to=sjust@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sugangli@winlab.rutgers.edu \
    /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.