image_types.bbclass: use 4096 instead of 8192 bytes-per-inode

The following changes since commit 33fa7c8f28d343ecec354a551d45f23643becd59:

pixbufcache: Fix librsvg-native build (2014-03-18 23:05:23 +0000)

are available in the git repository at:

git://git.openembedded.org/openembedded-core-contrib rbt/inode
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/inode

Robert Yang (1):
image_types.bbclass: use 4096 instead of 8192 bytes-per-inode

 meta/classes/image_types.bbclass | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

1.8.3.1

The image not correctly created if 'ptest-pkgs' is in IMAGE_FEATURES, this is because there is no free inode left. We can use 4096 instead of 8192 bytes-per-inode to fix the problem, and most of the distributions us 4096, such as Ubuntu, Suse, Fedora and CentOS.

There are another problems:
* There are error message when there is no free inode left if we run the mke2fs command manually, but they are not in log.do_rootfs.

* The image generation doesn't stop when error happens because mke2fs doesn't return failed for this case.

Will fix them in other threads.

[YOCTO #5957]

---
 meta/classes/image_types.bbclass | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

index 5864006..b693317 100644
@@ -103,9 +103,9 @@ JFFS2_ERASEBLOCK ?= "0x40000"
 EXTRA_IMAGECMD_jffs2 ?= "--pad ${JFFS2_ENDIANNESS} --eraseblock=${JFFS2_ERASEBLOCK} --no-cleanmarkers"
 
 # Change these if you want default mkfs behavior (i.e. create minimal inode number)
-EXTRA_IMAGECMD_ext2 ?= "-i 8192"
-EXTRA_IMAGECMD_ext3 ?= "-i 8192"
-EXTRA_IMAGECMD_ext4 ?= "-i 8192"
+EXTRA_IMAGECMD_ext2 ?= "-i 4096"
+EXTRA_IMAGECMD_ext3 ?= "-i 4096"
+EXTRA_IMAGECMD_ext4 ?= "-i 4096"
 EXTRA_IMAGECMD_btrfs ?= ""
 EXTRA_IMAGECMD_elf ?= ""
 

1.8.3.1