CEPH filesystem development
 help / color / mirror / Atom feed
From: Alex Elder <elder@inktank.com>
To: brady <brady@lamphost.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Character limit for rbd block device
Date: Mon, 26 Nov 2012 21:00:55 -0600	[thread overview]
Message-ID: <50B42CE7.3080506@inktank.com> (raw)
In-Reply-To: <50B404DA.50805@lamphost.com>

On 11/26/2012 06:10 PM, brady wrote:
> Hello,
>     I have a general question. Is there a specific character limit for
> rbd block devices? In attempting to map a block device with a name that
> is 36 characters or more, I am getting the following error:
> 
> rbd map (36+ character name) --user admin --secret /etc/ceph/keyring.key
> add failed: (2) No such file or directory

We can set the maximum supported length almost arbitrarily high,
although we use the image name in a path component.  Linux limits
such file names to 255 bytes normally.

As Josh said, the limit is higher than what you mention.  Do
you have any thoughts on what constitutes a reasonable limit?
Are you using some sort of naming convention that produces
your 36+ byte image names?

Thanks.

					-Alex

>     When using the same command to map a device with 35 characters or
> less, the device is mapped as expected. Any insight into this issue
> would be greatly appreciated.
> 
> -Brady
> -- 
> 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


      parent reply	other threads:[~2012-11-27  3:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27  0:10 Character limit for rbd block device brady
2012-11-27  0:52 ` Josh Durgin
2012-11-27 21:32   ` brady
2012-11-27  3:00 ` Alex Elder [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=50B42CE7.3080506@inktank.com \
    --to=elder@inktank.com \
    --cc=brady@lamphost.com \
    --cc=ceph-devel@vger.kernel.org \
    /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