From: Maor Lipchuk <mlipchuk@redhat.com>
To: qemu-devel@nongnu.org
Cc: Nir Soffer <nsoffer@redhat.com>, Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] Is qemu-img amend an atomic operation?
Date: Mon, 19 Dec 2016 14:49:38 +0200 [thread overview]
Message-ID: <CAJ1JNOc_HHVZOx_qZTWK=U_dn6_69UDnD3eDmoEVU4mYnCLC2w@mail.gmail.com> (raw)
In-Reply-To: <CAJ1JNOepVarVZZeVKaUN+5TTRFz-BKU+WcEu5koUR_W2YrFADA@mail.gmail.com>
On Mon, Dec 19, 2016 at 2:47 PM, Maor Lipchuk <mlipchuk@redhat.com> wrote:
> Hi All,
>
> Does amend considered as an atomic operation or should we mark a volume as
> ILLEGAL once the amend operation fails?
>
> also, if I call amend, but downgrade the QCOW volume compatibility level
> from 1.1 to 0.10, is that atomic as well (or not, based on the answer on
> the previous question)?
>
> Regards,
> Maor
>
Adding also Nir and Kevin to the thread.
next prev parent reply other threads:[~2016-12-19 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 12:47 [Qemu-devel] Is qemu-img amend an atomic operation? Maor Lipchuk
2016-12-19 12:49 ` Maor Lipchuk [this message]
2016-12-19 13:10 ` Kevin Wolf
2016-12-19 13:39 ` Maor Lipchuk
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='CAJ1JNOc_HHVZOx_qZTWK=U_dn6_69UDnD3eDmoEVU4mYnCLC2w@mail.gmail.com' \
--to=mlipchuk@redhat.com \
--cc=kwolf@redhat.com \
--cc=nsoffer@redhat.com \
--cc=qemu-devel@nongnu.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).