On Tue, Jan 30, 2018 at 02:34:33PM +0800, Fam Zheng wrote: > Signed-off-by: Fam Zheng <[email protected]> > Signed-off-by: Kevin Wolf <[email protected]> > --- > qemu-img.texi | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/qemu-img.texi b/qemu-img.texi > index 60a0e080c6..ec7e2f5d1e 100644 > --- a/qemu-img.texi > +++ b/qemu-img.texi > @@ -86,6 +86,13 @@ exclusive with the @var{-O} parameters. It is currently > required to also use > the @var{-n} parameter to skip image creation. This restriction may be > relaxed > in a future release. > > +@item --force-share (-U) > +If specified, @code{qemu-img} will open the image in shared mode, allowing > +concurrent writers.
This wording confuses me. It makes me think of multiple processes
writing to the image at the same time...
> This option is only allowed when opening images in read-only mode.
...but later it turns out "concurrent writers" means there can be at
most 1 writing process and multiple reading processes.
How about merging the two statements?
"If specified, allows @code{qemu-img} to open the image in read-only
mode even if another process already has it open for writing."
signature.asc
Description: PGP signature
