All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@inktank.com>
To: Eric_YH_Chen@wiwynn.com
Cc: ceph-devel@vger.kernel.org, Chris_YT_Huang@wiwynn.com,
	Victor_CY_Chang@wiwynn.com
Subject: Re: rbd map error with new rbd format
Date: Fri, 19 Oct 2012 16:52:42 -0700	[thread overview]
Message-ID: <5081E7CA.2080801@inktank.com> (raw)
In-Reply-To: <60E83269D669544E8069A09CB69135EA02DF21@GDC-CLDMBX-P02.whq.wistron>

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

  reply	other threads:[~2012-10-19 23:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18  8:01 rbd map error with new rbd format Eric_YH_Chen
2012-10-19 23:52 ` Josh Durgin [this message]
2012-10-22  9:04 ` Eric_YH_Chen
2012-10-22 14:27   ` Gregory Farnum
  -- strict thread matches above, loose matches on Subject: below --
2012-09-12 12:56 Martin Mailand
2012-09-12 14:28 ` Josh Durgin

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=5081E7CA.2080801@inktank.com \
    --to=josh.durgin@inktank.com \
    --cc=Chris_YT_Huang@wiwynn.com \
    --cc=Eric_YH_Chen@wiwynn.com \
    --cc=Victor_CY_Chang@wiwynn.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.