qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Changlimin <changlimin@h3c.com>, Fam Zheng <famz@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Qemu-block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] Block format 'raw' does not support the option 'locking' when disable image locking with option locking=off
Date: Thu, 26 Oct 2017 09:32:50 +0200	[thread overview]
Message-ID: <c9c95933-c70c-f16c-dd70-9b66aede987a@redhat.com> (raw)
In-Reply-To: <BC29A004BA570342A4CC0044A3845572CFCE5D44@H3CMLB12-EX.srv.huawei-3com.com>

[-- Attachment #1: Type: text/plain, Size: 348 bytes --]

On 2017-10-26 09:18, Changlimin wrote:
> If the qcow2 file is created with preallocation=full, I think metadata will not corrupt when it is shared between two vms? Snapshot is not required. 
> 
> Is this right?

I wouldn't count on it.

If you really want to take the risk, you can probably use the
file.locking=off option again.

Max


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]

  reply	other threads:[~2017-10-26  7:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25  8:15 [Qemu-devel] Block format 'raw' does not support the option 'locking' when disable image locking with option locking=off Changlimin
2017-10-25 13:31 ` Fam Zheng
2017-10-26  1:06   ` Changlimin
2017-10-26  7:11     ` Max Reitz
2017-10-26  7:18       ` Changlimin
2017-10-26  7:32         ` Max Reitz [this message]
2017-10-27  1:28           ` Changlimin
2017-10-31 20:00         ` John Snow

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=c9c95933-c70c-f16c-dd70-9b66aede987a@redhat.com \
    --to=mreitz@redhat.com \
    --cc=changlimin@h3c.com \
    --cc=famz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).