Am 14.10.2012 07:30, schrieb Kashyap Chamarthy:
> From a6233277e17338f571dda27cd9192d764f824b18 Mon Sep 17 00:00:00 2001
> From: Kashyap Chamarthy <[email protected]>
> Date: Sun, 14 Oct 2012 09:51:18 +0530
> Subject: [PATCH v2] qemu-img: document 'info --backing-chain'
>
> Signed-off-by: Kashyap Chamarthy <[email protected]>
> @@ -137,6 +141,19 @@ from the displayed size. If VM snapshots are stored in
> the disk image,
> they are displayed too. The command can output in the format @var{ofmt}
> which is either @code{human} or @code{json}.
>
> +If a disk image has a backing file chain, information about each disk image
> in
> +the chain can be recursively enumerated by using the option
> @code{--backing-chain}.
> +
> +For instance, if you have an image chain like:
> +
> + base.qcow2 <- snap1.qcow2 <- snap2.qcow2
> +
> +To enumerate information about each disk image in the above chain, starting
> from top to base, do:
> +
> + @example
> + qemu-img info --backing-chain snap2.qcow2
> + @end example
> +
> @item snapshot [-l | -a @var{snapshot} | -c @var{snapshot} | -d
> @var{snapshot} ] @var{filename}
>
> List, apply, create or delete snapshots in image @var{filename}.
For me, this is rendered as:
For instance, if you have an image chain like:
base.qcow2 E<lt>- snap1.qcow2 E<lt>- snap2.qcow2
To enumerate information about each disk image in the above
chain, starting from top to base, do:
@example
qemu-img info --backing-chain snap2.qcow2
@end example
That is, the arrows aren't quite right and @example is included
literally. Please fix and resubmit.
Kevin
