Skip to contentSkip to conversation

qemu-img.texi: Describe data_file and data_file_raw

PATCH Superseded Han Han 3 participants 4 messages Oct 18, 2019 – Oct 21, 2019

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore

Han Han

author
#0 lore raw

PATCH 1/1 qemu-img.texi: Describe data_file and data_file_raw

https://bugzilla.redhat.com/show_bug.cgi?id=1763105

---
 qemu-img.texi | 10 ++++++++++
 1 file changed, 10 insertions(+)
qemu-img.texi +10 -0
index b5156d6316..44596c2d93 100644
@@ -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.
+
+@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
Signature · 1 line
2.20.1
Reviewed-by on v1 1/1
#1 lore raw

[cc qemu-block]

Quoted 7 lines · Han Han

https://bugzilla.redhat.com/show_bug.cgi?id=1763105

---
  qemu-img.texi | 10 ++++++++++
  1 file changed, 10 insertions(+)
Quoted 22 lines
qemu-img.texi +10 -0
index b5156d6316..44596c2d93 100644
@@ -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.
+
+@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
Signature · 3 lines
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org
#2 lore raw
In reply to Han Han

CC qemu-block

Quoted 12 lines · Han Han

https://bugzilla.redhat.com/show_bug.cgi?id=1763105

---
 qemu-img.texi | 10 ++++++++++
 1 file changed, 10 insertions(+)
qemu-img.texi +0 -0
index b5156d6316..44596c2d93 100644

qemu-img.texi file which is COW and has data blocks already, it couldn't be changed to NOCOW · line 770

Quoted 8 lines
qemu-img.texi +5 -0
@@ -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."

Quoted 9 lines
qemu-img.texi +5 -0
+@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
author
#3 lore raw
Quoted 25 lines · John Snow

CC qemu-block

qemu-img.texi file which is COW and has data blocks already, it

Quoted 12 lines · Han Han

https://bugzilla.redhat.com/show_bug.cgi?id=1763105

---
 qemu-img.texi | 10 ++++++++++
 1 file changed, 10 insertions(+)
qemu-img.texi +0 -0
index b5156d6316..44596c2d93 100644
@@ -763,6 +763,16 @@ file which is COW and has data blocks already, it

couldn't be changed to NOCOW

qemu-img.texi file which is COW and has data blocks already, it · line 763

Quoted 1 line
qemu-img.texi +0 -0
 by setting @code{nocow=on}. One can issue @code{lsattr filename} to

check if

qemu-img.texi file which is COW and has data blocks already, it couldn't be changed to NOCOW

Quoted 4 lines
qemu-img.texi +2 -0
 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

qemu-img.texi file which is COW and has data blocks already, it · line 768

Quoted 1 line
qemu-img.texi +1 -0
+opening the image. If the option is used, qcow2 file only stores the

metadata

Quoted 9 lines

qemu-img.texi file which is COW and has data blocks already, it · line 770

Quoted 2 lines
qemu-img.texi +2 -0
+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."

Thanks for your advice. I will update it in v2.

Quoted 13 lines

qemu-img.texi file which is COW and has data blocks already, it · line 772

Quoted 3 lines
qemu-img.texi +2 -0
+@item data_file_raw
+This option requires @option{data_file}. If this option is set to

@code{on},

Quoted 7 lines
qemu-img.texi +3 -0
+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
Signature · 8 lines
Best regards,
-----------------------------------
Han Han
Quality Engineer
Redhat.

Email: [email protected]
Phone: +861065339333