All of lore.kernel.org
 help / color / mirror / Atom feed
* too tight inode limits on ext4?
@ 2013-07-26 13:27 Riku Voipio
  2013-07-26 15:13 ` Jonathan Liu
  0 siblings, 1 reply; 2+ messages in thread
From: Riku Voipio @ 2013-07-26 13:27 UTC (permalink / raw)
  To: openembedded-core

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: too tight inode limits on ext4?
  2013-07-26 13:27 too tight inode limits on ext4? Riku Voipio
@ 2013-07-26 15:13 ` Jonathan Liu
  0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Liu @ 2013-07-26 15:13 UTC (permalink / raw)
  To: Riku Voipio; +Cc: openembedded-core

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-07-26 15:18 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-07-26 13:27 too tight inode limits on ext4? Riku Voipio
2013-07-26 15:13 ` Jonathan Liu

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.