From: Oliver Francke <Oliver.Francke@filoo.de>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: RBD/qemu-1.7.0 memory leak with drive_mirror/live-migration
Date: Tue, 17 Dec 2013 13:45:22 +0100 [thread overview]
Message-ID: <52B04762.50306@filoo.de> (raw)
Hi *,
I just tried a feature for live-migration via:
drive_mirror -f virtio0 rbd:123123/virtio0 rbd
in a qemu-monitoring-session.
One immediately can see some memory consumption... never getting
released again. Additionally the block-job never ends, even after X/X
bytes completed.
You can cancel the job, memory still occupied, after another try more
RSS-memory gets filled.
Same procedure with qcow2 does not need any more memory, and the job
gets cleared after completion.
Possibly @Josh: any idea? Logfiles with debug_what=? needed? ;)
Thnx in @vance,
Oliver.
--
Oliver Francke
filoo GmbH
Moltkestraße 25a
33330 Gütersloh
HRB4355 AG Gütersloh
Geschäftsführer: J.Rehpöhler | C.Kunz
Folgen Sie uns auf Twitter: http://twitter.com/filoogmbh
--
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
reply other threads:[~2013-12-17 12:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52B04762.50306@filoo.de \
--to=oliver.francke@filoo.de \
--cc=ceph-devel@vger.kernel.org \
/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.