All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Zafman <dzafman@redhat.com>
To: Sage Weil <sweil@redhat.com>, ceph-devel@vger.kernel.org
Subject: Re: ceph-objectstore-tool import failures
Date: Fri, 19 Jun 2015 20:16:30 -0700	[thread overview]
Message-ID: <5584DB0E.3000503@redhat.com> (raw)
In-Reply-To: <5584D213.80405@redhat.com>


This ghobject_t which has a pool of -3 is part of the export.   This 
caused the assert:

Read -3/1c/temp_recovering_1.1c_33'50_39_head/head

This was added by "osd: use per-pool temp poolid for temp objects" 
18eb2a5fea9b0af74a171c3717d1c91766b15f0c in your branch.

You should skip it on export or recreate it on import with special handling.

David

On 6/19/15 7:38 PM, David Zafman wrote:
>
> Have not seen this as an assert before.  Given the code below in 
> do_import() of master branch the assert is impossible (?).
>
>   if (!curmap.have_pg_pool(pgid.pgid.m_pool)) {
>     cerr << "Pool " << pgid.pgid.m_pool << " no longer exists" << 
> std::endl;
>     // Special exit code for this error, used by test code
>     return 10;  // Positive return means exit status
>   }
>
>
> David
>
> On 6/19/15 7:25 PM, Sage Weil wrote:
>> Hey David,
>>
>> On this run
>>
>>     /a/sage-2015-06-18_15:51:18-rados-wip-temp---basic-multi/939648
>>
>> ceph-objectstore-tool is failing to import a pg because the pool doesn't
>> exist.  It looks like the thrasher is doing an export+import and racing
>> with a test that is tearing down a pool.  The crash is
>>
>>   ceph version 9.0.1-955-ge274efa
>> (e274efa450e99a68c02bcb713c8837d7809f1ec3)
>>   1: ceph-objectstore-tool() [0xa26335]
>>   2: (()+0xfcb0) [0x7f10cef18cb0]
>>   3: (gsignal()+0x35) [0x7f10cd5af425]
>>   4: (abort()+0x17b) [0x7f10cd5b2b8b]
>>   5: (__gnu_cxx::__verbose_terminate_handler()+0x11d) [0x7f10cdf0269d]
>>   6: (()+0xb5846) [0x7f10cdf00846]
>>   7: (()+0xb5873) [0x7f10cdf00873]
>>   8: (()+0xb596e) [0x7f10cdf0096e]
>>   9: (ceph::__ceph_assert_fail(char const*, char const*, int, char
>> const*)+0x259) [0xb0ce09]
>>   10: (ObjectStoreTool::get_object(ObjectStore*, coll_t,
>> ceph::buffer::list&, OSDMap&, bool*)+0x143f) [0x64829f]
>>   11: (ObjectStoreTool::do_import(ObjectStore*, OSDSuperblock&, bool,
>> std::string)+0x13dd) [0x64a62d]
>>   12: (main()+0x3017) [0x632037]
>>   13: (__libc_start_main()+0xed) [0x7f10cd59a76d]
>>   14: ceph-objectstore-tool() [0x639119]
>>
>> I don't think this is related to my branch.. but maybe?  Have you seen
>> this?  I rebased onto latest master yesterday.
>>
>> sage
>
> -- 
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in

  reply	other threads:[~2015-06-20  3:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-20  2:25 ceph-objectstore-tool import failures Sage Weil
2015-06-20  2:38 ` David Zafman
2015-06-20  3:16   ` David Zafman [this message]
2015-07-06 20:28     ` Sage Weil
2015-07-06 23:32       ` David Zafman
2015-07-07 17:00         ` Sage Weil
2015-07-07 17:12           ` Samuel Just
2015-07-07 17:22             ` Sage Weil
2015-07-07 17:34               ` Samuel Just
2015-07-07 20:56                 ` David Zafman
2015-07-07 21:10                   ` 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=5584DB0E.3000503@redhat.com \
    --to=dzafman@redhat.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 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.