All of lore.kernel.org
 help / color / mirror / Atom feed
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 21:22:01 +0200	[thread overview]
Message-ID: <55AE9BD9.6010801@profihost.ag> (raw)
In-Reply-To: <1828157940.1473499.1437499191528.JavaMail.zimbra@redhat.com>


Am 21.07.2015 um 19:19 schrieb Jason Dillaman:
> Does this still occur if you export the images to the console (i.e. "rbd export cephstor/disk-116@snap - > dump_file")?
>
> Would it be possible for you to provide logs from the two "rbd export" runs on your smallest VM image?  If so, please add the following to the "[client]" section of your ceph.conf:
>
>    log file = /valid/path/to/logs/$name.$pid.log
>    debug rbd = 20
>
> I opened a ticket [1] where you can attach the logs (if they aren't too large).
>
> [1] http://tracker.ceph.com/issues/12422

Will post some more details to the tracker in a few hours. It seems it 
is related to using discard inside guest but not on the FS the osd is on.

Stefan

  reply	other threads:[~2015-07-21 19:22 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
2015-07-21 17:19     ` Jason Dillaman
2015-07-21 19:22       ` Stefan Priebe [this message]
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=55AE9BD9.6010801@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.