From: Alex Elder <elder@inktank.com>
To: Chris Dunlop <chris@onthe.net.au>
Cc: ceph-devel@vger.kernel.org
Subject: Re: krbd + format=2 ?
Date: Fri, 07 Jun 2013 11:54:20 -0500 [thread overview]
Message-ID: <51B2103C.7040402@inktank.com> (raw)
In-Reply-To: <20130603092428.GB28293@onthe.net.au>
On 06/03/2013 04:24 AM, Chris Dunlop wrote:
> G'day,
>
> Sage's recent pull message to Linus said:
>
> ----
> Please pull the following Ceph patches from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus
>
> This is a big pull. Most of it is culmination of Alex's work to implement
> RBD image layering, which is now complete (yay!).
> ----
>
> Am I correct in thinking "RBD image layering... is now complete"
> implies there should be full(?) support for format=2?
>
> I pulled the for-linus branch (@ 3abef3b) on top of 3.10.0-rc4, and it's
> letting me map a format=2 image (created under bobtail), however reading
> from the block device returns zeros rather than the data. The same image
> correctly shows data (NTFS filesystem) when mounted into kvm using librbd.
Have you tried using a format 2 image that you created using
the Linux rbd environment? It would be good to know whether
that works for you.
Can you also send me the result of running each of these commands:
foo=$(rados get --pool=rbd rbd_id.xxx - | strings)
rados ls --pool=rbd | grep rbd_data | grep "${foo}"
unset foo
Thanks.
-Alex
>
> ----
> # uname -r
> 3.10.0-rc4-00010-g0326739
> # rbd ls -l
> NAME SIZE PARENT FMT PROT LOCK
> xxx 1536G 2
> # rbd map rbd/xxx
> # rbd showmapped
> id pool image snap device
> 1 rbd xxx - /dev/rbd1
> # dd if=/dev/rbd1 of=/tmp/xxx count=20480
> 20480+0 records in
> 20480+0 records out
> 10485760 bytes (10 MB) copied, 0.757754 s, 13.8 MB/s
> # od -c /tmp/xxx | less
> 0000000 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
> *
> 50000000
> ----
>
>
> Cheers,
>
> Chris
> --
> 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
>
next prev parent reply other threads:[~2013-06-07 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 9:24 krbd + format=2 ? Chris Dunlop
2013-06-07 16:54 ` Alex Elder [this message]
2013-06-08 2:48 ` Chris Dunlop
2013-06-12 4:59 ` Chris Dunlop
2013-06-13 3:56 ` Josh Durgin
2013-06-13 6:35 ` Chris Dunlop
2013-06-15 17:01 ` Alex Elder
2013-07-04 14:45 ` Laurent Barbe
2013-07-05 4:12 ` Sage Weil
2013-07-05 7:39 ` Laurent Barbe
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=51B2103C.7040402@inktank.com \
--to=elder@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=chris@onthe.net.au \
/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.