From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Cui, Dexuan" <dexuan.cui@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/6] Setup for VMDK to use Direct Disk
Date: Sun, 01 Apr 2012 20:43:14 +0100 [thread overview]
Message-ID: <1627697.cshU2EUhO7@helios> (raw)
In-Reply-To: <A25F549E4D43CD42B4C02DF47A1913230FCEC5F0@SHSMSX102.ccr.corp.intel.com>
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
prev parent reply other threads:[~2012-04-01 19:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 5:42 [PATCH 0/6] Setup for VMDK to use Direct Disk Saul Wold
2012-03-27 5:42 ` [PATCH 1/6] self-hosted-image: pre-populate the builder user with poky source Saul Wold
2012-03-28 15:35 ` Cui, Dexuan
2012-03-28 21:07 ` Saul Wold
2012-03-29 7:15 ` Cui, Dexuan
2012-03-28 20:45 ` Paul Eggleton
2012-03-28 21:08 ` Saul Wold
2012-03-27 5:42 ` [PATCH 2/6] image-vmdk: Add symbolic link for a short named vmdk image Saul Wold
2012-03-27 5:42 ` [PATCH 3/6] boot-directdisk: Fix Block Calcuation Saul Wold
2012-03-27 5:42 ` [PATCH 4/6] vmdk: Update for direstdisk Saul Wold
2012-03-27 5:42 ` [PATCH 5/6] builder: Enable auto starting of Hob Saul Wold
2012-03-27 5:43 ` [PATCH 6/6] image_types: remove duplicate setting of -i for inode count Saul Wold
2012-03-27 14:37 ` [PATCH 0/6] Setup for VMDK to use Direct Disk Paul Eggleton
2012-03-27 18:16 ` Saul Wold
2012-03-27 20:21 ` Paul Eggleton
2012-03-27 20:45 ` João Henrique Freitas
2012-03-28 15:21 ` Cui, Dexuan
2012-03-30 14:17 ` Paul Eggleton
2012-03-30 21:16 ` Cui, Dexuan
2012-03-31 5:11 ` Cui, Dexuan
2012-04-01 10:28 ` Cui, Dexuan
2012-04-01 19:43 ` Paul Eggleton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1627697.cshU2EUhO7@helios \
--to=paul.eggleton@linux.intel.com \
--cc=dexuan.cui@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.