rbd map error with new rbd format

rbd map error with new rbd format

[Martin Mailand]

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.

-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:

Re: rbd map error with new rbd format

[Josh Durgin]

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:

Re: rbd map error with new rbd format

[Eric_YH_Chen]

Hi, Josh:

> 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.

As you mentioned before, http://www.spinics.net/lists/ceph-devel/msg08857.html
The kernel rbd is not ready at September, so we cannot map rbd to a device. 
Would you mind to estimate when will be available? And which version of kernel? (3.5 or 3.6?)  
Thanks!

Re: rbd map error with new rbd format

[Josh Durgin]

On 10/18/2012 01:01 AM, Eric_YH_Chen@wiwynn.com wrote:
> Hi, Josh:
>
>> 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.
>
> As you mentioned before, http://www.spinics.net/lists/ceph-devel/msg08857.html
> The kernel rbd is not ready at September, so we cannot map rbd to a device.
> Would you mind to estimate when will be available? And which version of kernel? (3.5 or 3.6?)
> Thanks!

At this point format 2 is understood by the kernel, and the
infrastructure for opening parent images and the I/O path
for clones is in progress. We estimate about 4-8 weeks for this,
but you should check back then.

Kernel 3.6 was already released, so this would probably go into 3.8 or
3.9.

Josh

RE: rbd map error with new rbd format

[Eric_YH_Chen]

> At this point format 2 is understood by the kernel, and the
> infrastructure for opening parent images and the I/O path
> for clones is in progress. We estimate about 4-8 weeks for this,
> but you should check back then.
> Kernel 3.6 was already released, so this would probably go into 3.8 or
> 3.9.

Hi Josh:

Please let me clarify some point. 
If we want to map an RBD image to a kernel object, it may not ready until kernel 3.8 or 3.9.
But if we want to running qemu with RBD, it is ready in kernel 3.6, since QEMU can access it via librbd directly.
Do I correct? Thanks!


-----Original Message-----
From: ceph-devel-owner@vger.kernel.org [mailto:ceph-devel-owner@vger.kernel.org] On Behalf Of Eric_YH_Chen@wiwynn.com
Sent: Thursday, October 18, 2012 4:01 PM
To: ceph-devel@vger.kernel.org
Cc: Chris YT Huang/WYHQ/Wiwynn; Victor CY Chang/WYHQ/Wiwynn
Subject: Re: rbd map error with new rbd format

Hi, Josh:

> 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.

As you mentioned before, http://www.spinics.net/lists/ceph-devel/msg08857.html
The kernel rbd is not ready at September, so we cannot map rbd to a device. 
Would you mind to estimate when will be available? And which version of kernel? (3.5 or 3.6?) Thanks!
--
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

Re: rbd map error with new rbd format

[Gregory Farnum]

On Mon, Oct 22, 2012 at 2:04 AM,  <Eric_YH_Chen@wiwynn.com> wrote:
>
>> At this point format 2 is understood by the kernel, and the
>> infrastructure for opening parent images and the I/O path
>> for clones is in progress. We estimate about 4-8 weeks for this,
>> but you should check back then.
>> Kernel 3.6 was already released, so this would probably go into 3.8 or
>> 3.9.
>
> Hi Josh:
>
> Please let me clarify some point.
> If we want to map an RBD image to a kernel object, it may not ready until kernel 3.8 or 3.9.
Right.

> But if we want to running qemu with RBD, it is ready in kernel 3.6, since QEMU can access it via librbd directly.
It doesn't even need to be kernel 3.6 — it just needs to be a
sufficiently new version of librbd. Hurray userspace! :)
--
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