From: Jonathan Liu <net147@gmail.com>
To: Riku Voipio <riku.voipio@linaro.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: too tight inode limits on ext4?
Date: Sat, 27 Jul 2013 01:13:58 +1000 [thread overview]
Message-ID: <51F29236.70003@gmail.com> (raw)
In-Reply-To: <CAAqcGH=ouV4fgpR629AVG2+J2SVY6vbPTyD0JatyMX72oVn-pQ@mail.gmail.com>
On 26/07/2013 11:27 PM, Riku Voipio wrote:
> So the image has plenty of space:
>
> root@genericarmv8:~# df -h
>
> Filesystem Size Used Avail Use% Mounted on
> /dev/root 2.3G 961M 1.2G 45% /
>
> root@genericarmv8:~#
>
> but only 48 free inodes:
>
> root@genericarmv8:~# df -i
> Filesystem Inodes IUsed IFree IUse% Mounted on
> /dev/root 34440 34392 48 100% /
>
> ext3 image is much more sensible:
>
> root@genericarmv8:~# df -i
> Filesystem Inodes IUsed IFree IUse% Mounted on
> /dev/root 293888 34392 259496 12% /
> e
>
> I understand that the E in OE is about embedded, but still only 48 free
> inodes seems a bit too steep. I would presume the amount of free inodes
> should be about the same for both ext3 and ext4.
>
> Also fiddling with EXTRA_IMAGECMD_ext4 doesn't seem to have any effect,
> so currently ext4 images are not very useful.
>
> Riku
Try Robert Yang's patches which build ext4 using mkfs.ext4 and debugfs
rather than genext2fs:
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=robert/image
Regards,
Jonathan
prev parent reply other threads:[~2013-07-26 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 13:27 too tight inode limits on ext4? Riku Voipio
2013-07-26 15:13 ` Jonathan Liu [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=51F29236.70003@gmail.com \
--to=net147@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=riku.voipio@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox