From: Jason Dillaman <dillaman@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: ceph-devel@vger.kernel.org
Subject: Re: upstream/firefly exporting the same snap 2 times results in different exports
Date: Tue, 21 Jul 2015 10:32:44 -0400 (EDT) [thread overview]
Message-ID: <1431119614.1353345.1437489164103.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <55AE3B3A.2040902@profihost.ag>
Any chance that the snapshot was just created prior to the first export and you have a process actively writing to the image?
--
Jason Dillaman
Red Hat
dillaman@redhat.com
http://www.redhat.com
----- Original Message -----
> From: "Stefan Priebe - Profihost AG" <s.priebe@profihost.ag>
> To: ceph-devel@vger.kernel.org
> Sent: Tuesday, July 21, 2015 8:29:46 AM
> Subject: upstream/firefly exporting the same snap 2 times results in different exports
>
> Hi,
>
> i remember there was a bug before in ceph not sure in which release
> where exporting the same rbd snap multiple times results in different
> raw images.
>
> Currently running upstream/firefly and i'm seeing the same again.
>
>
> # rbd export cephstor/disk-116@snap dump1
> # sleep 10
> # rbd export cephstor/disk-116@snap dump2
>
> # md5sum -b dump*
> b89198f118de59b3aa832db1bfddaf8f *dump1
> f63ed9345ac2d5898483531e473772b1 *dump2
>
> Can anybody help?
>
> Greets,
> Stefan
> --
> 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:[~2015-07-21 14:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 12:29 upstream/firefly exporting the same snap 2 times results in different exports Stefan Priebe - Profihost AG
2015-07-21 14:32 ` Jason Dillaman [this message]
2015-07-21 16:55 ` Stefan Priebe
2015-07-21 17:19 ` Jason Dillaman
2015-07-21 19:22 ` Stefan Priebe
2015-07-21 19:46 ` Josh Durgin
2015-07-21 19:48 ` Stefan Priebe
2015-07-21 20:48 ` Jason Dillaman
2015-07-21 19:52 ` Stefan Priebe
2015-07-21 20:50 ` Josh Durgin
2015-07-22 7:03 ` Stefan Priebe - Profihost AG
2015-07-22 10:27 ` Nathan Cutler
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=1431119614.1353345.1437489164103.JavaMail.zimbra@redhat.com \
--to=dillaman@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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.