<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><DIV>thanks for the note, will try the lastest svn code.</DIV>
<DIV> </DIV>
<DIV>I agree that not many people would bother using split2G disks.</DIV>
<DIV> </DIV>
<DIV>We have a user using our MyOldPCs converter, and his external disk is FAT32, so in this kind of rare cases, we had to use split2G as FAT32 has a 4G file size limit.<BR><BR>--- On <B>Mon, 11/2/09, Klaus Espenlaub <I><Klaus.Espenlaub@Sun.COM></I></B> wrote:<BR></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(16,16,255) 2px solid"><BR>From: Klaus Espenlaub <Klaus.Espenlaub@Sun.COM><BR>Subject: Re: [vbox-dev] split 2g vmdk seems to have some issues<BR>To: "Huihong Luo" <huisinro@yahoo.com><BR>Cc: vbox-dev@virtualbox.org<BR>Date: Monday, November 2, 2009, 8:12 AM<BR><BR>
<DIV class=plainMail>Huihong Luo wrote:<BR>> thansk for the quick fixes<BR>> I verified that work well now.<BR>> yes, those two issues were caused by same bug<BR><BR>Bad news: the fix was incorrect, and it turned out it only worked around a bug elsewehere. Additionally the "fix" had the side effect of breaking raw partition VMDK files.<BR><BR><A href="http://www.virtualbox.org/ticket/5355" target=_blank>http://www.virtualbox.org/ticket/5355</A><BR><BR>Latest svn should have a better fix.<BR><BR>Note that all split VMDK files created by VirtualBox up to 3.0.10 are subtly broken (they incorrectly specify a non-zero sector offset for all extents but the first one).<BR><BR>It's possible to automatically repair such images, but this takes quite some effort, as the extent description is not touched by VirtualBox for existing images. I don't believe many people have split VMDK files created by VirtualBox, so I'm not sure if it's worth the
effort.<BR><BR>Klaus<BR><BR>> --- On *Tue, 10/27/09, Klaus Espenlaub /<<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=Klaus.Espenlaub@Sun.COM" ymailto="mailto:Klaus.Espenlaub@Sun.COM">Klaus.Espenlaub@Sun.COM</A>>/* wrote:<BR>> <BR>> <BR>> From: Klaus Espenlaub <<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=Klaus.Espenlaub@Sun.COM" ymailto="mailto:Klaus.Espenlaub@Sun.COM">Klaus.Espenlaub@Sun.COM</A>><BR>> Subject: Re: [vbox-dev] split 2g vmdk seems to have some issues<BR>> To: "Klaus Espenlaub" <<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=Klaus.Espenlaub@Sun.COM" ymailto="mailto:Klaus.Espenlaub@Sun.COM">Klaus.Espenlaub@Sun.COM</A>><BR>> Cc: "Huihong Luo" <<A href="http://us.mc343.mail.yahoo.com/mc/compose?to=huisinro@yahoo.com" ymailto="mailto:huisinro@yahoo.com">huisinro@yahoo.com</A>>, <A
href="http://us.mc343.mail.yahoo.com/mc/compose?to=vbox-dev@virtualbox.org" ymailto="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</A><BR>> Date: Tuesday, October 27, 2009, 5:01 AM<BR>> <BR>> Klaus Espenlaub wrote:<BR>> > Huihong Luo wrote:<BR>> >> for example<BR>> >> (1) create a 40G disk as split2G, then attach to a xp guest vm,<BR>> it won't format<BR>> ><BR>> > Confirmed. Investigating the reason for the incorrect reporting<BR>> of VERR_OUT_OF_RANGE for perfectly valid sector numbers.<BR>> ><BR>> >> (2) VDCopy(VD_VMDK_IMAGE_FLAGS_SPLIT_2G) throws<BR>> VERR_OUT_OF_RANGE sometimes<BR>>
><BR>> > This is certainly caused by the same issue. However I don't see<BR>> any reason why this should be "sometimes", as the out of range check<BR>> is against data which isn't supposed to change after an image is<BR>> created.<BR>> <BR>> As suspected, there was just one bug which caused the misbehavior.<BR>> <BR>> Fixed in the OSE repository, and will be fixed as well in VirtualBox<BR>> 3.0.10.<BR>> <BR>> Klaus<BR>> <BR>> <BR>> ------------------------------------------------------------------------<BR>> <BR>> _______________________________________________<BR>> vbox-dev mailing list<BR>> <A href="http://us.mc343.mail.yahoo.com/mc/compose?to=vbox-dev@virtualbox.org"
ymailto="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</A><BR>> <A href="http://vbox.innotek.de/mailman/listinfo/vbox-dev" target=_blank>http://vbox.innotek.de/mailman/listinfo/vbox-dev</A><BR></DIV></BLOCKQUOTE></td></tr></table>