search for: raw_measur

...t.raw’ then output.raw > will be a sparse file, and that's the file size I'd expect measure to > give us for "required size" (of course "fully allocated size" would be > the virtual size, and that is correct). > > It does look as if the block/raw-format.c:raw_measure function is wrong. No, it is correct. Its output is what the file size will be. For raw images, that is the same as the virtual disk size. Not all blocks in the file will be actually allocated, but the file size is what 'ls -l' prints, not what 'du' prints (for regular files). I...

Am 15.08.2018 um 12:26 hat Richard W.M. Jones geschrieben: > On Tue, Aug 14, 2018 at 09:31:06PM +0300, Nir Soffer wrote: > > On Tue, Aug 14, 2018 at 8:29 PM Richard W.M. Jones <rjones@redhat.com> > > wrote: > > > > > This option prints the estimated size of the data that will be copied > > > from the source disk. > > > > > > For

...convert ... -O raw output.raw’ then output.raw will be a sparse file, and that's the file size I'd expect measure to give us for "required size" (of course "fully allocated size" would be the virtual size, and that is correct). It does look as if the block/raw-format.c:raw_measure function is wrong. In any case we can use the qcow2 estimate for our purposes as it will be near enough what we need (a rough estimate of the size of the copy). Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: h...

On Tue, Aug 14, 2018 at 09:31:06PM +0300, Nir Soffer wrote: > On Tue, Aug 14, 2018 at 8:29 PM Richard W.M. Jones <rjones@redhat.com> > wrote: > > > This option prints the estimated size of the data that will be copied > > from the source disk. > > > > For interest, the test prints: > > > > 3747840 ../test-data/phony-guests/windows.img > >