[OE-core] [PATCH 0/6] Setup for VMDK to use Direct Disk

[Paul Eggleton]

On Sunday 01 April 2012 10:28:35 Cui, Dexuan wrote:
> Hi Paul, I believe this is true:
> genext2fs-1.4.1 can create a corrupt file system when
> the size of the file system exceeds some limit.
> 
> e.g., when I create an image of 2.8GB, the image can be mounted
> properly, but when I create an image of about 4.5GB(yes, I found
> genext2fs-1.4.1 is actually able to create an image of 4.5GB; I also
> found it's unable to create an image of about 5.5GB, always
> reporting "couldn't allocate a block (no free space)"),
> the generated image can show something like this when it's
> booted:
> 
> EXT3-fs error (device hda2): ext3_lookup: deleted inode referenced...
> 
> However, with Corey's patches (from the genext2fs's mailing list)
> applied, I can't see the issues.

I can confirm this.

With these patches applied I also compared (a) using genext2fs to create a 
30GB rootfs, and (b) letting genext2fs create a filesystem with just enough 
space and then resizing it to 30GB with resize2fs. There was no benefit in the 
latter - it took 5 minutes longer.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre