From: John Snow <jsnow@redhat.com>
To: Han Han <hhan@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Qemu-block <qemu-block@nongnu.org>
Subject: Re: [PATCH] qemu-img.texi: Describe data_file and data_file_raw
Date: Fri, 18 Oct 2019 16:58:41 -0400 [thread overview]
Message-ID: <39bde897-fd65-582d-7d2e-8aec27254898@redhat.com> (raw)
In-Reply-To: <20191018095924.4409-1-hhan@redhat.com>
CC qemu-block
On 10/18/19 5:59 AM, Han Han wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1763105
>
> Signed-off-by: Han Han <hhan@redhat.com>
> ---
> qemu-img.texi | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/qemu-img.texi b/qemu-img.texi
> index b5156d6316..44596c2d93 100644
> --- a/qemu-img.texi
> +++ b/qemu-img.texi
> @@ -763,6 +763,16 @@ file which is COW and has data blocks already, it couldn't be changed to NOCOW
> by setting @code{nocow=on}. One can issue @code{lsattr filename} to check if
> the NOCOW flag is set or not (Capital 'C' is NOCOW flag).
>
> +@item data_file
> +File name of data file that is stored in the image and used as a default for
> +opening the image. If the option is used, qcow2 file only stores the metadata
> +of the image.
> +
This is a little unclear, and seems to imply the data file is stored
*IN* the image.
"Optional filename to be used as a data store for this qcow2 file. If
this option is used, the qcow2 file only stores metadata for this image."
> +@item data_file_raw
> +This option requires @option{data_file}. If this option is set to @code{on},
> +qemu will always keep the external data file consistent as a standalone
> +read-only raw image. Default value is @code{off}.
> +
> @end table
>
> @item Other
>
next prev parent reply other threads:[~2019-10-18 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 9:59 [PATCH] qemu-img.texi: Describe data_file and data_file_raw Han Han
2019-10-18 14:13 ` Eric Blake
2019-10-18 20:58 ` John Snow [this message]
2019-10-21 1:06 ` Han Han
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=39bde897-fd65-582d-7d2e-8aec27254898@redhat.com \
--to=jsnow@redhat.com \
--cc=hhan@redhat.com \
--cc=kwolf@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).