All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@dreamhost.com>
To: Eric_YH_Chen@wistron.com
Cc: ceph-devel@vger.kernel.org, Chris_YT_Huang@wistron.com
Subject: Re: Hang when mapping a long name rbd image
Date: Fri, 16 Dec 2011 18:40:01 -0800	[thread overview]
Message-ID: <4EEC0101.3030905@dreamhost.com> (raw)
In-Reply-To: <8512670932FB654F81AF0FEF1BE6D49DA2ECA6@WHQBEMAIL1.whq.wistron>

On 12/16/2011 06:21 PM, Eric_YH_Chen@wistron.com wrote:
> Hi, all:
>
> My ceph version is
> ceph version 0.39 (commit:321ecdaba2ceeddb0789d8f4b7180a8ea5785d83)
>
> When I try to map a long name rbd image to device, it would hang for
> long time.
>
> For example:
> sudo rbd map iqn.2012-01.com.sample:storage.ttttttt --secret
> /etc/ceph/secretfile sudo rbd map iqn.2012-01.com.sample:storage.abcdef
> --secret /etc/ceph/secretfile

The limit was increased in this commit:

commit 224736d9113ab4a7cf3f05c05377492bd99b4b02
Author: Stratos Psomadakis <psomas@grnet.gr>
Date:   Thu Nov 10 15:45:37 2011 +0200

     libceph: Allocate larger oid buffer in request msgs

     ceph_osd_request struct allocates a 40-byte buffer for object names.
     RBD image names can be up to 96 chars long (100 with the .rbd suffix),
     which results in the object name for the image being truncated, and a
     subsequent map failure.

     Increase the oid buffer in request messages, in order to avoid the
     truncation.

There is still an outstanding issue with the limits in the kernel not 
being enforced by userspace tools though 
(http://tracker.newdream.net/issues/1701).

>
> It would not hang at every long name image, however, it only happens
> when the image name is very long.
>
> Is it a known issue?
>
> Thanks!


      reply	other threads:[~2011-12-17  2:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17  2:21 Hang when mapping a long name rbd image Eric_YH_Chen
2011-12-17  2:40 ` Josh Durgin [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=4EEC0101.3030905@dreamhost.com \
    --to=josh.durgin@dreamhost.com \
    --cc=Chris_YT_Huang@wistron.com \
    --cc=Eric_YH_Chen@wistron.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 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.