From: Stefan Priebe <s.priebe@profihost.ag>
To: Jason Dillaman <dillaman@redhat.com>
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 18:55:43 +0200 [thread overview]
Message-ID: <55AE798F.1010206@profihost.ag> (raw)
In-Reply-To: <1431119614.1353345.1437489164103.JavaMail.zimbra@redhat.com>
Am 21.07.2015 um 16:32 schrieb Jason Dillaman:
> Any chance that the snapshot was just created prior to the first export and you have a process actively writing to the image?
>
Sadly not. I executed those commands exactly as i've posted manually at
bash.
I can reproduce this at 5 different ceph cluster and 500 vms each.
Stefan
next prev parent reply other threads:[~2015-07-21 16:55 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
2015-07-21 16:55 ` Stefan Priebe [this message]
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=55AE798F.1010206@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=dillaman@redhat.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.