CEPH filesystem development
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: David Zafman <dzafman@redhat.com>, Sage Weil <sweil@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: new OSD re-using old OSD id fails to boot
Date: Wed, 9 Dec 2015 14:06:55 +0100	[thread overview]
Message-ID: <5668276F.90803@dachary.org> (raw)
In-Reply-To: <56678036.5050909@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 743 bytes --]



On 09/12/2015 02:13, David Zafman wrote:
> 
> Remember I really think we want a disk replacement feature that would retain the OSD id so that it avoids unnecessary data movement.  See tracker http://tracker.ceph.com/issues/13732

I remember this, yes, it is a good idea :-)  Would that help fix http://tracker.ceph.com/issues/13988 ?

> David
> 
> On 12/5/15 8:49 AM, Loic Dachary wrote:
>> Hi Sage,
>>
>> The problem described at "new OSD re-using old OSD id fails to boot" http://tracker.ceph.com/issues/13988 consistently fails the ceph-disk suite on master. I wonder if it could be a side effect of the recent optimizations introduced in the monitor ?
>>
>> Cheers
>>
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      parent reply	other threads:[~2015-12-09 13:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-05 16:49 new OSD re-using old OSD id fails to boot Loic Dachary
2015-12-09  1:13 ` David Zafman
2015-12-09  2:50   ` Sage Weil
2015-12-09 10:39     ` Wei-Chung Cheng
2015-12-09 13:08       ` Loic Dachary
2015-12-09 14:00       ` Sage Weil
2015-12-09 19:55       ` David Zafman
2015-12-09 20:08         ` Sage Weil
2015-12-09 13:06   ` Loic Dachary [this message]

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=5668276F.90803@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dzafman@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox