All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <elder@inktank.com>
To: Christian Huang <ythuang@gmail.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: limit of maximum number of rbd devices that can be mapped
Date: Wed, 17 Oct 2012 21:18:25 -0500	[thread overview]
Message-ID: <507F66F1.4000509@inktank.com> (raw)
In-Reply-To: <CAP5wSLc0fGo03Sh0mric3pb_yNkOY=0bEkMHR0Nmq2u8F0nJAw@mail.gmail.com>

On 10/17/2012 09:15 PM, Christian Huang wrote:
> Hi,
>     what is the maximum number of rbd devices that can be mapped on a
> single host?
>     we recently did a test to mount a large number of rbd devices and
> hit a wall around 230
>     with the following message

That sounds about right.  We were just discussing this earlier
this week.  It's limited at the moment by the number of major
device numbers available on the system, and I think you found
that limit.  We would obviously like to have a solution for
this but we've only just started considering options.

					-Alex

> with 230 rbd devices already mapped, the next one yielded this.
> Console output
> wistor@wistor-002:~$ sudo rbd map test299
> add failed: (16) Device or resource busy
> 
> dmesg
> [77962.346749] register_blkdev: failed to get major for rbd229
> 
> Chris.
> --
> 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:[~2012-10-18  2:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18  2:15 limit of maximum number of rbd devices that can be mapped Christian Huang
2012-10-18  2:18 ` Alex Elder [this message]
2012-10-18  3:12   ` Christian Huang
2012-11-02 10:59   ` Danny Al-Gaaf
2012-11-02 11:22     ` Sage Weil
2012-11-02 12:28       ` Danny Al-Gaaf

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=507F66F1.4000509@inktank.com \
    --to=elder@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ythuang@gmail.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.