All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: ceph stays degraded after crushmap rearrangement
Date: Sat, 05 Jan 2013 19:05:11 +0100	[thread overview]
Message-ID: <50E86B57.4090708@profihost.ag> (raw)
In-Reply-To: <alpine.DEB.2.00.1301050955150.15430@cobra.newdream.net>

Hi,

Am 05.01.2013 18:56, schrieb Sage Weil:
>> But my rbd images are gone ?!
>>
>> [1202: ~]# rbd -p kvmpool1 ls
>> [1202: ~]#
>
> Oh.. I think this is related to the librados/librbd compatibility issue I
> mentioned yesterday.  Please make sure the clients (librados, librbd) are
> also running the latest testing branch.

ah OK  - thanks that's it - ceph has now also recovered completely with 
old crushmap.

OK now back to my original problem.

i wanted to change from this:
-----------------------------------------
...

rack D2-switchA {
         id -100         # do not change unnecessarily
         # weight 12.000
         alg straw
         hash 0  # rjenkins1
         item server1263 weight 4.000
         item server1264 weight 4.000
         item server1265 weight 4.000
}
rack D2-switchB {
         id -101         # do not change unnecessarily
         # weight 12.000
         alg straw
         hash 0  # rjenkins1
         item server1266 weight 4.000
         item server1267 weight 4.000
         item server1268 weight 4.000
}
root root {
         id -10000               # do not change unnecessarily
         # weight 24.000
         alg straw
         hash 0  # rjenkins1
         item D2-switchA weight 12.000
         item D2-switchB weight 12.000
}

...
-----------------------------------------

to this one:

-----------------------------------------
...

rack D2 {
         id -100         # do not change unnecessarily
         # weight 24.000
         alg straw
         hash 0  # rjenkins1
         item cloud1-1263 weight 4.000
         item cloud1-1264 weight 4.000
         item cloud1-1265 weight 4.000
         item cloud1-1266 weight 4.000
         item cloud1-1267 weight 4.000
         item cloud1-1268 weight 4.000
}
root root {
         id -10000               # do not change unnecessarily
         # weight 24.000
         alg straw
         hash 0  # rjenkins1
         item D2 weight 24.000
}

...
-----------------------------------------

This was where all problems started. Is this wrong? / not possible?

Greets,
Stefan

  reply	other threads:[~2013-01-05 18:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05 16:40 ceph stays degraded after crushmap rearrangement Stefan Priebe
2013-01-05 17:03 ` Stefan Priebe
2013-01-05 17:06   ` Sage Weil
2013-01-05 17:11     ` Stefan Priebe
2013-01-05 17:16       ` Stefan Priebe
2013-01-05 17:40         ` Sage Weil
2013-01-05 17:46           ` Stefan Priebe
2013-01-05 17:56             ` Sage Weil
2013-01-05 18:05               ` Stefan Priebe [this message]
2013-01-05 18:15                 ` Stefan Priebe
2013-01-05 18:46                 ` Sage Weil

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=50E86B57.4090708@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@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.