Hello Cristian, I tried to reproduce the issue you mentioned, however the straightforward scenario creates the disk as you expect it to be (sparse), not with its full size.
Please provide some more information regarding the use case you brought up: 1. Was the disk created from template? 2. Was the disk with snapshots? 3. Was it NFS or SCSI? 4. Where (and how) did you see that the exported disk size is full ? 5. Which build (or from which approximate date) is your ovirt ? You can also try to run the below command on vdsm to check the size: getVolumeSize <sdUUID> <spUUID> <imgUUID> <volUUID> (by invoking it via vdsClient) vdsClient 0 getVolumeSize <sdUUID> <spUUID> <imgUUID> <volUUID> Thank you, Alissa > From: "Cristian Falcas" <[email protected]> > To: "Alexandre Santos" <[email protected]> > Cc: [email protected] > Sent: Monday, November 19, 2012 6:06:03 PM > Subject: Re: [Users] export VM > > > Shrinking can also be made with the normal cp from linux: > > cp --sparse=always > > This will create usually files smaller then the original even. > > But maybe this can be fixed from the source. Exporting some images > that have 10s/100s of gigabytes but only use a few gb is time and > space consuming with no benefits. > > best regards, > > > > > > On Mon, Nov 19, 2012 at 2:00 PM, Alexandre Santos < > [email protected] > wrote: > > > Hi Cristian, > I don't know what ovirt is doing but if the final file is a raw > image, you can shrink it with qemu-img and transform it in a qcow2. > What I think was on the head of who implemented this is that you > export a VM to a NAS that has normally Teras of space, so it is more > compatible to save it in raw format. My 2 cents :-) > > Alex > > > > > 2012/11/19 Cristian Falcas < [email protected] > > > > > > > > > > > On Mon, Nov 19, 2012 at 12:51 PM, Alexandre Santos < > [email protected] > wrote: > > > > 2012/11/18 Cristian Falcas < [email protected] > > > > > > Hi all, > > I see that exporting a VM with ThinProvisioning will make an image > with the full disk size, instead of the currently used size: > - VM has a 20GB disk > - installed OS is taking 1.3GB > - exported disk is taking 20GB > > Is this mandatory? Couldn't the export make a file with the same > size, also sparse? It seems it only does a copy of the folder and > the normal linux cp can make a sparse copy. > > thank you, > Cristian Falcas > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > > > Is it exporting a a raw image, right? > > Alex > > > Hi Alex, > > I don't understand what you mean by raw. > > I was saying that the same file could be copied as a sparse file > instead. > > Cristian > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
