> 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@xxxxxxxxxxxxxxx [mailto:ceph-devel-owner@xxxxxxxxxxxxxxx] On Behalf Of Eric_YH_Chen@xxxxxxxxxx Sent: Thursday, October 18, 2012 4:01 PM To: ceph-devel@xxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
