From: Josh Durgin <josh.durgin@inktank.com>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: other rbd stuff
Date: Tue, 16 Apr 2013 15:43:11 -0700 [thread overview]
Message-ID: <516DD3FF.6020009@inktank.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1304161446540.5978@cobra.newdream.net>
On 04/16/2013 03:02 PM, Sage Weil wrote:
> - wip-4531 looks good. should i merge it?
Yes
> - figured out the DiffIterate failures (rbd caching), see wip-4683.
> flushing from diff_iterate should be fine right?
It should use _flush() so that it doesn't count as a flush coming from
an upper layer.
> - the qemu-iotests are failing because of the rbd progress on stderr.
> sent a patch to qemu list with a 2>/dev/null. note that qemu-iotests is
> not part of qemu.git, so our test script should clone from there instead.
> or we can make our own copy of the old standalone repo and host it
> ourselves...
Until we have a qemu gitbuilder, we should copy the old qemu-iotests
repo. The tests depend heavily on the version of qemu used (output
differences plus using new features and fixes for old bugs).
Josh
prev parent reply other threads:[~2013-04-16 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 22:02 other rbd stuff Sage Weil
2013-04-16 22:43 ` Josh Durgin [this message]
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=516DD3FF.6020009@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.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.