qcow2 info: show highest-allocation and num-free-bytes
Status from this message: Applied all. Thanks.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v2 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | block-qcow2: keep highest allocated byteblock-qcow2.c | +34 | 0 replies | |
| 2/5 | block-qcow2: export highest_allocated through BlockDriverInfo and get_info()block-qcow2.c block.h | +2 | 0 replies | |
| 3/5 | info blockstats: show highest_allocated if existsblock.c | +6 | 0 replies | |
| 4/5 | qcow2 format: keep 'num_free_bytes', and show it upon 'info blockstats'block-qcow2.c block.c block.h | +32 | 0 replies | |
| 5/5 | qemu-img: info: show highest_alloc and num_free_bytes if existqemu-img.c | +4 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [Qemu-devel] [PATCH 0/5 v2] qcow2 info: show highest-allocation and num-free-bytes
Hello,
The following 5 enhance "info blockstats" for qcow2 images (and other formats that implement bdrv_get_info), to show higest-allocated-offset and number-of-free-bytes (below the higest-allocated-offset) of the image.
One of the main usage for this information is to know and act upon a case of end-of-storage-space. Instead of waiting for -ENOSPACE (which now may cause the VM to stop), one can define a threshold and extend the diskspace allocated for the image.
This info is also good for management systems, so they can report the user disk space status.
Also with highest_alloc and num_free_bytes, we can have a pretty good idea about how fragmented a qcow2 images is, and try to defragment it later.
Patches 1,2,3, Provides information about the highest allocated byte (offset) Patch 4, Provides information about the number of free bytes
below highest_alloc.
Patch 5, Provides info about highest_alloc and num_free_bytes through
qemu-img info
Changes from v1: better description of use cases.
Regards,
Uri.