From: brady <brady@lamphost.com>
To: Josh Durgin <josh.durgin@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Character limit for rbd block device
Date: Tue, 27 Nov 2012 13:32:54 -0800 [thread overview]
Message-ID: <50B53186.1040807@lamphost.com> (raw)
In-Reply-To: <50B40ED5.7050307@inktank.com>
On 11/26/2012 04:52 PM, Josh Durgin wrote:
> On 11/26/2012 04: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
>>
>> 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
>
> Which kernel version are you using?
>
> A year ago there was a 40-char limit on objects names in the kernel's
> libceph module, hence the failure at 36 char rbd image names (36 char
> name + ".rbd" is the format 1 header object name).
>
> This was extended to a 96-char limit in linux 3.2. There's no real limit
> in userspace still (http://tracker.newdream.net/issues/1701).
>
> Josh
>
Thanks, Josh. This information was exactly what we were looking for.
Looks like a version issue that we will need to work around. Thanks again!
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
next prev parent reply other threads:[~2012-11-27 21:33 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 [this message]
2012-11-27 3:00 ` Alex Elder
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=50B53186.1040807@lamphost.com \
--to=brady@lamphost.com \
--cc=ceph-devel@vger.kernel.org \
--cc=josh.durgin@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.