trouble with ext2 filesystem

trouble with ext2 filesystem

[Alessandro GARDICH]

[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]

Hi all

I notice a problem of the generated filesystem

MACHINE = "qemux86"
DISTRO = "kaeilos"
IMAGE_FSTYPES = "ext2"
IMAGE_ROOTFS_SIZE = "102400"


building console-image I obtain a .ext2 filesystem with
Free blocks:              89357
Free inodes:              87

notice ... only 87 free inodes !!!

after my small and trial patch this is the result
Free blocks:              86302
Free inodes:              24527

maybe 4096 could be too small ... maybe 10k could be good, your choice.

At now I modify qemux86.conf cause usually EXTRA_IMAGECMD is in the 
machine config file, but to add hardware specific parameters (flash size 
  and erase size). I'm not sure if is the right place. Probably in the 
distro configuration could be better.

thanks in advance



-- 
  /------------------------------------------------\
|     Alessandro Gardich : gremlin#gremlin!it      |
  >------------------------------------------------<
|  I never saw a wild thing sorry for itself.      |
|  A small bird will drop frozen dead from a bough |
|  without ever having felt sorry for itself.      |
  \------------------------------------------------/

diff --git a/conf/machine/qemux86.conf b/conf/machine/qemux86.conf
index c251216..23436ce 100644
--- a/conf/machine/qemux86.conf
+++ b/conf/machine/qemux86.conf
@@ -16,3 +16,5 @@ PREFERRED_PROVIDER_virtual/kernel = "linux-rp"
 
 GLIBC_ADDONS = "nptl"
 GLIBC_EXTRA_OECONF = "--with-tls"
+
+EXTRA_IMAGECMD_ext2 = "-i 4096"

Re: trouble with ext2 filesystem

[Phil Blundell]

On Sat, 2009-05-23 at 22:23 +0200, Alessandro GARDICH wrote:
> At now I modify qemux86.conf cause usually EXTRA_IMAGECMD is in the 
> machine config file, but to add hardware specific parameters (flash size 
>   and erase size). I'm not sure if is the right place. Probably in the 
> distro configuration could be better.

The distro config probably is the right place for this.  After all, the
number of inodes you need depends primarily on the number of files that
you're going to ship in the rootfs, and that in turn is primarily
influenced by the DISTRO's policies rather than by any inherent aspect
of the MACHINE.

The other uses of EXTRA_IMAGECMD that I guess you're thinking of are
mostly to do with jffs2 parameters, which are rather different in that
they're determined by the specifics of the hardware in use and hence do
go with the MACHINE rather than the DISTRO.

p.

Re: trouble with ext2 filesystem

[Alessandro GARDICH]

[-- Attachment #1: Type: text/plain, Size: 2150 bytes --]

Phil Blundell wrote:
> On Sat, 2009-05-23 at 22:23 +0200, Alessandro GARDICH wrote:
>> At now I modify qemux86.conf cause usually EXTRA_IMAGECMD is in the 
>> machine config file, but to add hardware specific parameters (flash size 
>>   and erase size). I'm not sure if is the right place. Probably in the 
>> distro configuration could be better.
> 
> The distro config probably is the right place for this.  After all, the
> number of inodes you need depends primarily on the number of files that
> you're going to ship in the rootfs, and that in turn is primarily
> influenced by the DISTRO's policies rather than by any inherent aspect
> of the MACHINE.
> 
> The other uses of EXTRA_IMAGECMD that I guess you're thinking of are
> mostly to do with jffs2 parameters, which are rather different in that
> they're determined by the specifics of the hardware in use and hence do
> go with the MACHINE rather than the DISTRO.
> 
> p.
> 
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

true, reform the patch for kaeilos.conf



-- 
  /------------------------------------------------\
|     Alessandro Gardich : gremlin#gremlin!it      |
  >------------------------------------------------<
|  I never saw a wild thing sorry for itself.      |
|  A small bird will drop frozen dead from a bough |
|  without ever having felt sorry for itself.      |
  \------------------------------------------------/

diff --git a/conf/distro/kaeilos.conf b/conf/distro/kaeilos.conf
index 718239b..94387e3 100644
--- a/conf/distro/kaeilos.conf
+++ b/conf/distro/kaeilos.conf
@@ -42,6 +42,8 @@ DISTRO_TYPE ?= "debug"
 # Also, it appears that no locales fit in 16Mb for now. "C" locale rules!
 IMAGE_LINGUAS = '${@base_less_or_equal("ROOT_FLASH_SIZE", "16", "", "en-us", d)}'
 
+# increase inode/block ratio for ext2 filesystem 
+EXTRA_IMAGECMD_ext2 = "-i 4096"
 
 # set feed path variables
 FEED_BASEPATH = "feeds/2008/${ANGSTROM_PKG_FORMAT}/${LIBC}/"

Re: trouble with ext2 filesystem

[Alessandro GARDICH]

[-- Attachment #1: Type: text/plain, Size: 2150 bytes --]

Phil Blundell wrote:
> On Sat, 2009-05-23 at 22:23 +0200, Alessandro GARDICH wrote:
>> At now I modify qemux86.conf cause usually EXTRA_IMAGECMD is in the 
>> machine config file, but to add hardware specific parameters (flash size 
>>   and erase size). I'm not sure if is the right place. Probably in the 
>> distro configuration could be better.
> 
> The distro config probably is the right place for this.  After all, the
> number of inodes you need depends primarily on the number of files that
> you're going to ship in the rootfs, and that in turn is primarily
> influenced by the DISTRO's policies rather than by any inherent aspect
> of the MACHINE.
> 
> The other uses of EXTRA_IMAGECMD that I guess you're thinking of are
> mostly to do with jffs2 parameters, which are rather different in that
> they're determined by the specifics of the hardware in use and hence do
> go with the MACHINE rather than the DISTRO.
> 
> p.
> 
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

true, reform the patch for kaeilos.conf



-- 
  /------------------------------------------------\
|     Alessandro Gardich : gremlin#gremlin!it      |
  >------------------------------------------------<
|  I never saw a wild thing sorry for itself.      |
|  A small bird will drop frozen dead from a bough |
|  without ever having felt sorry for itself.      |
  \------------------------------------------------/

diff --git a/conf/distro/kaeilos.conf b/conf/distro/kaeilos.conf
index 718239b..94387e3 100644
--- a/conf/distro/kaeilos.conf
+++ b/conf/distro/kaeilos.conf
@@ -42,6 +42,8 @@ DISTRO_TYPE ?= "debug"
 # Also, it appears that no locales fit in 16Mb for now. "C" locale rules!
 IMAGE_LINGUAS = '${@base_less_or_equal("ROOT_FLASH_SIZE", "16", "", "en-us", d)}'
 
+# increase inode/block ratio for ext2 filesystem 
+EXTRA_IMAGECMD_ext2 = "-i 4096"
 
 # set feed path variables
 FEED_BASEPATH = "feeds/2008/${ANGSTROM_PKG_FORMAT}/${LIBC}/"

Re: trouble with ext2 filesystem

[Alessandro GARDICH]

[-- Attachment #1: Type: text/plain, Size: 2150 bytes --]

Phil Blundell wrote:
> On Sat, 2009-05-23 at 22:23 +0200, Alessandro GARDICH wrote:
>> At now I modify qemux86.conf cause usually EXTRA_IMAGECMD is in the 
>> machine config file, but to add hardware specific parameters (flash size 
>>   and erase size). I'm not sure if is the right place. Probably in the 
>> distro configuration could be better.
> 
> The distro config probably is the right place for this.  After all, the
> number of inodes you need depends primarily on the number of files that
> you're going to ship in the rootfs, and that in turn is primarily
> influenced by the DISTRO's policies rather than by any inherent aspect
> of the MACHINE.
> 
> The other uses of EXTRA_IMAGECMD that I guess you're thinking of are
> mostly to do with jffs2 parameters, which are rather different in that
> they're determined by the specifics of the hardware in use and hence do
> go with the MACHINE rather than the DISTRO.
> 
> p.
> 
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

true, reform the patch for kaeilos.conf



-- 
  /------------------------------------------------\
|     Alessandro Gardich : gremlin#gremlin!it      |
  >------------------------------------------------<
|  I never saw a wild thing sorry for itself.      |
|  A small bird will drop frozen dead from a bough |
|  without ever having felt sorry for itself.      |
  \------------------------------------------------/

diff --git a/conf/distro/kaeilos.conf b/conf/distro/kaeilos.conf
index 718239b..94387e3 100644
--- a/conf/distro/kaeilos.conf
+++ b/conf/distro/kaeilos.conf
@@ -42,6 +42,8 @@ DISTRO_TYPE ?= "debug"
 # Also, it appears that no locales fit in 16Mb for now. "C" locale rules!
 IMAGE_LINGUAS = '${@base_less_or_equal("ROOT_FLASH_SIZE", "16", "", "en-us", d)}'
 
+# increase inode/block ratio for ext2 filesystem 
+EXTRA_IMAGECMD_ext2 = "-i 4096"
 
 # set feed path variables
 FEED_BASEPATH = "feeds/2008/${ANGSTROM_PKG_FORMAT}/${LIBC}/"

Re: trouble with ext2 filesystem

[Marco Cavallini]

Alessandro GARDICH ha scritto:
> Hi all
> 
> I notice a problem of the generated filesystem
> 
> MACHINE = "qemux86"
> DISTRO = "kaeilos"
> IMAGE_FSTYPES = "ext2"
> IMAGE_ROOTFS_SIZE = "102400"
> 
> 
> building console-image I obtain a .ext2 filesystem with
> Free blocks:              89357
> Free inodes:              87
> 
> notice ... only 87 free inodes !!!
> 
> after my small and trial patch this is the result
> Free blocks:              86302
> Free inodes:              24527
> 
> maybe 4096 could be too small ... maybe 10k could be good, your choice.
> 
> At now I modify qemux86.conf cause usually EXTRA_IMAGECMD is in the
> machine config file, but to add hardware specific parameters (flash size
>  and erase size). I'm not sure if is the right place. Probably in the
> distro configuration could be better.
> 
> thanks in advance
> 
> 

Thank you for the patch.

Acked-by: Marco Cavallini  <m.cavallini@koansoftware.com>

Re: trouble with ext2 filesystem

[Alessandro GARDICH]

Marco Cavallini wrote:
> Alessandro GARDICH ha scritto:
>   
>> Hi all
>>
>> I notice a problem of the generated filesystem
>>
>> MACHINE = "qemux86"
>> DISTRO = "kaeilos"
>> IMAGE_FSTYPES = "ext2"
>> IMAGE_ROOTFS_SIZE = "102400"
>>
>>
>> building console-image I obtain a .ext2 filesystem with
>> Free blocks:              89357
>> Free inodes:              87
>>
>> notice ... only 87 free inodes !!!
>>
>> after my small and trial patch this is the result
>> Free blocks:              86302
>> Free inodes:              24527
>>
>> maybe 4096 could be too small ... maybe 10k could be good, your choice.
>>
>> At now I modify qemux86.conf cause usually EXTRA_IMAGECMD is in the
>> machine config file, but to add hardware specific parameters (flash size
>>  and erase size). I'm not sure if is the right place. Probably in the
>> distro configuration could be better.
>>
>> thanks in advance
>>
>>
>>     
>
> Thank you for the patch.
>
> Acked-by: Marco Cavallini  <m.cavallini@koansoftware.com>
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>   
nope ... my mistake ... the patch to ack is the other,
that patch kaeilos.conf and not qemux86.conf


-- 
 /-------------------------------------------------------------\
|           Alessandro Gardich : gremlin@gremlin.it             |
 >-------------------------------------------------------------<
|  I never saw a wild thing sorry for itself.                   |
|  A small bird will drop frozen dead from a bough              |
|  without ever having felt sorry for itself.                   |
 \-------------------------------------------------------------/

Re: trouble with ext2 filesystem

[Marco Cavallini]

Alessandro GARDICH ha scritto:
> Phil Blundell wrote:
>> On Sat, 2009-05-23 at 22:23 +0200, Alessandro GARDICH wrote:
>>> At now I modify qemux86.conf cause usually EXTRA_IMAGECMD is in the
>>> machine config file, but to add hardware specific parameters (flash
>>> size   and erase size). I'm not sure if is the right place. Probably
>>> in the distro configuration could be better.
>>
>> The distro config probably is the right place for this.  After all, the
>> number of inodes you need depends primarily on the number of files that
>> you're going to ship in the rootfs, and that in turn is primarily
>> influenced by the DISTRO's policies rather than by any inherent aspect
>> of the MACHINE.
>>
>> The other uses of EXTRA_IMAGECMD that I guess you're thinking of are
>> mostly to do with jffs2 parameters, which are rather different in that
>> they're determined by the specifics of the hardware in use and hence do
>> go with the MACHINE rather than the DISTRO.
>>
>> p.
>>
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 
> true, reform the patch for kaeilos.conf
> 
> 
> 
> 

Thank you for the patch.

Acked-by: Marco Cavallini  <m.cavallini@koansoftware.com>