On Sat, 10 Mar 2007, Mike Shultz wrote: > Hello. I'm trying to plug our g4u disk images into virtual machines on > my workstation. Problem is, there's limited space on this machine. > > The image I'm trying to write to the virtual disk is only 2.8GB but when > doing a 'slurpdisk' it writes much more then that(up to 9GB before the > VM errored out). > > Why is g4u trying to write more data then is necessary? If g4u only > uses 'dd' to create the image, I'd imagine it would just be a block by > block copy excluding blank/empty blocks. Is there any way I can go > about having it write only the necessary data?
g4u doesn't know about what data is 'necessary' or not, it creates a 1:1 image of the source disk, and then later writes the exact amount of data back. If y ou have a 9GB disk with ~no data at the end that shouldn't do much harm to abort earlier if your target disk is too small. When putting a 'big' image onto a 'small' disk you should just make sure that the 'extra' space is on a separate partition or in unpartitioned space, else nasty things may happen to your data. - Hubert ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ g4u-help mailing list g4u-help@feyrer.de https://lists.sourceforge.net/lists/listinfo/g4u-help
