From: Josh Durgin <josh.durgin@inktank.com>
To: Karol Jurak <karol.jurak@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Modifying RBD image changes it's snapshot
Date: Wed, 26 Jun 2013 11:15:34 -0700 [thread overview]
Message-ID: <51CB2FC6.6070803@inktank.com> (raw)
In-Reply-To: <1805042.yIbHV06QAO@karol-esprimo-p5925>
On 06/26/2013 05:40 AM, Karol Jurak wrote:
> Hi,
>
> I'm using ceph 0.56.6 and kernel 3.9.7 and it looks like modifying RBD image
> also changes it's snapshot. I can reproduce this as follows:
>
> # create and map an image
> rbd create --size 128 test-1
> rbd map test-1
>
> # write some data to the image
> dd if=/dev/zero of=/dev/rbd/rbd/test-1 bs=1M count=128
>
> # create and map a snapshot
> rbd snap create test-1@snap-1
> rbd map test-1@snap-1
>
> # verify that image and snapshot are identical
> md5sum /dev/rbd/rbd/test-1 /dev/rbd/rbd/test-1@snap-1
> fde9e0818281836e4fc0edfede2b8762 /dev/rbd/rbd/test-1
> fde9e0818281836e4fc0edfede2b8762 /dev/rbd/rbd/test-1@snap-1
>
> # modify the image
> dd if=/dev/urandom of=/dev/rbd/rbd/test-1 bs=512 count=1
>
> # compare checksums again
> md5sum /dev/rbd/rbd/test-1 /dev/rbd/rbd/test-1@snap-1
> 1d942c8a5bc7480cecb945ea0d020eed /dev/rbd/rbd/test-1
> 1d942c8a5bc7480cecb945ea0d020eed /dev/rbd/rbd/test-1@snap-1
>
> Checksums are identical although the snapshot isn't supposed to be modified.
>
Just reproduced on 3.10-rc7 as well. It seems the snapshot context
loading is broken for format 1 a t least, since unmapping and mapping
after the snapshot exists still has the same problem. I added
http://tracker.ceph.com/issues/5464 to track this.
Apparently the regression test for this hasn't been running, or we
would've caught this sooner.
Josh
next prev parent reply other threads:[~2013-06-26 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 12:40 Modifying RBD image changes it's snapshot Karol Jurak
2013-06-26 18:15 ` Josh Durgin [this message]
2013-06-26 21:42 ` Josh Durgin
2013-06-27 12:13 ` Karol Jurak
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=51CB2FC6.6070803@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=karol.jurak@gmail.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.