From: Josh Durgin <josh.durgin@inktank.com>
To: Martin Mailand <martin@tuxadero.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: rbd map error with new rbd format
Date: Wed, 12 Sep 2012 07:28:05 -0700 [thread overview]
Message-ID: <50509BF5.1040402@inktank.com> (raw)
In-Reply-To: <50508692.3050209@tuxadero.com>
On 09/12/2012 05:56 AM, Martin Mailand wrote:
> Hi,
>
> whilst testing the new rbd layering feature I found a problem with rbd
> map. It seems rbd map doesn't support the new format.
Yeah, format 2 and layering support is in progress for kernel rbd,
but not ready yet. The userspace side is all ready in the master
branch, but it takes more time to implement in the kernel.
Btw, instead of --new-format you should use --format 2. It's in
the man page in the master branch.
Josh
>
> -martin
>
>
> ceph -v
> ceph version 0.51-265-gc7d11cd
> (commit:c7d11cd7b813a47167108c160358f70ec1aab7d6)
>
>
> rbd create --size 100000 --new-format new
> rbd map new
> add failed: (2) No such file or directory
>
>
> rbd create --size 100000 old
> rbd map old
> rbd showmapped
> id pool image snap device
> 1 rbd old - /dev/rbd1
>
>
> rbd info new
> rbd image 'new':
> size 100000 MB in 25000 objects
> order 22 (4096 KB objects)
> block_name_prefix: rbd_data.101e1a89b511
> old format: False
> features: layering
> rbd info old
> rbd image 'old':
> size 100000 MB in 25000 objects
> order 22 (4096 KB objects)
> block_name_prefix: rb.0.1021.23697452
> old format: True
> features:
next prev parent reply other threads:[~2012-09-12 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 12:56 rbd map error with new rbd format Martin Mailand
2012-09-12 14:28 ` Josh Durgin [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-18 8:01 Eric_YH_Chen
2012-10-19 23:52 ` Josh Durgin
2012-10-22 9:04 ` Eric_YH_Chen
2012-10-22 14:27 ` Gregory Farnum
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=50509BF5.1040402@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=martin@tuxadero.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.