From: Vladimir Sementsov-Ogievskiy <vladimir.sementsov-ogievskiy@openvz.org>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, v.sementsov-og@mail.ru, jsnow@redhat.com,
qemu-devel@nongnu.org, armbru@redhat.com, hreitz@redhat.com,
vsementsov@openvz.org, stefanha@redhat.com, eblake@redhat.com
Subject: [PATCH v2 0/7] copy-before-write: on-cbw-error and cbw-timeout
Date: Fri, 1 Apr 2022 12:19:13 +0300 [thread overview]
Message-ID: <20220401091920.287612-1-vsementsov@openvz.org> (raw)
Hi all!
Here are two new options for copy-before-write filter:
on-cbw-error allows to alter the behavior on copy-before-write operation
failure: not break guest write but break the snapshot (and therefore
backup process)
cbw-timeout allows to limit cbw operation by some timeout.
So, for example, using cbw-timeout=60 and on-cbw-error=break-snapshot
you can be sure that guest write will not stuck for more than 60
seconds and will never fail due to backup problems.
This series unites and fixes my
"[PATCH 0/3] block: copy-before-write: on-cbw-error behavior" and
"[PATCH 0/4] block: copy-before-write: cbw-timeout"
Supersedes: <20220301205929.2006041-1-vsementsov@openvz.org>
Supersedes: <20220302162442.2052461-1-vsementsov@openvz.org>
Vladimir Sementsov-Ogievskiy (7):
block/copy-before-write: refactor option parsing
block/copy-before-write: add on-cbw-error open parameter
iotests: add copy-before-write: on-cbw-error tests
util: add qemu-co-timeout
block/block-copy: block_copy(): add timeout_ns parameter
block/copy-before-write: implement cbw-timeout option
iotests: copy-before-write: add cases for cbw-timeout option
block/block-copy.c | 26 ++-
block/copy-before-write.c | 136 +++++++++---
include/block/block-copy.h | 2 +-
include/qemu/coroutine.h | 13 ++
qapi/block-core.json | 30 ++-
tests/qemu-iotests/tests/copy-before-write | 206 ++++++++++++++++++
.../qemu-iotests/tests/copy-before-write.out | 5 +
util/meson.build | 1 +
util/qemu-co-timeout.c | 89 ++++++++
9 files changed, 464 insertions(+), 44 deletions(-)
create mode 100755 tests/qemu-iotests/tests/copy-before-write
create mode 100644 tests/qemu-iotests/tests/copy-before-write.out
create mode 100644 util/qemu-co-timeout.c
--
2.35.1
next reply other threads:[~2022-04-01 9:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 9:19 Vladimir Sementsov-Ogievskiy [this message]
2022-04-01 9:19 ` [PATCH v2 1/7] block/copy-before-write: refactor option parsing Vladimir Sementsov-Ogievskiy
2022-04-01 10:50 ` Hanna Reitz
2022-04-01 11:59 ` Vladimir Sementsov-Ogievskiy
2022-04-01 9:19 ` [PATCH v2 2/7] block/copy-before-write: add on-cbw-error open parameter Vladimir Sementsov-Ogievskiy
2022-04-01 11:58 ` Hanna Reitz
2022-04-01 12:18 ` Vladimir Sementsov-Ogievskiy
2022-04-01 9:19 ` [PATCH v2 3/7] iotests: add copy-before-write: on-cbw-error tests Vladimir Sementsov-Ogievskiy
2022-04-01 13:36 ` Hanna Reitz
2022-04-01 9:19 ` [PATCH v2 4/7] util: add qemu-co-timeout Vladimir Sementsov-Ogievskiy
2022-04-01 13:13 ` Hanna Reitz
2022-04-01 14:23 ` Vladimir Sementsov-Ogievskiy
2022-04-01 9:19 ` [PATCH v2 5/7] block/block-copy: block_copy(): add timeout_ns parameter Vladimir Sementsov-Ogievskiy
2022-04-01 13:16 ` Hanna Reitz
2022-04-01 13:22 ` Hanna Reitz
2022-04-01 16:08 ` Vladimir Sementsov-Ogievskiy
2022-04-04 14:39 ` Hanna Reitz
2022-04-05 11:33 ` Vladimir Sementsov-Ogievskiy
2022-04-06 16:10 ` Vladimir Sementsov-Ogievskiy
2022-04-01 9:19 ` [PATCH v2 6/7] block/copy-before-write: implement cbw-timeout option Vladimir Sementsov-Ogievskiy
2022-04-01 13:24 ` Hanna Reitz
2022-04-01 13:28 ` Hanna Reitz
2022-04-01 13:58 ` Vladimir Sementsov-Ogievskiy
2022-04-01 9:19 ` [PATCH v2 7/7] iotests: copy-before-write: add cases for " Vladimir Sementsov-Ogievskiy
2022-04-01 13:36 ` Hanna Reitz
2022-04-01 13:59 ` Vladimir Sementsov-Ogievskiy
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=20220401091920.287612-1-vsementsov@openvz.org \
--to=vladimir.sementsov-ogievskiy@openvz.org \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=v.sementsov-og@mail.ru \
--cc=vsementsov@openvz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).