From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.grid-net.com ([97.65.115.2]) by canuck.infradead.org with esmtp (Exim 4.72 #1 (Red Hat Linux)) id 1PNrI2-0006FE-V2 for linux-mtd@lists.infradead.org; Wed, 01 Dec 2010 18:20:27 +0000 Message-ID: <4CF691F0.9010607@grid-net.com> Date: Wed, 01 Dec 2010 10:20:32 -0800 From: Steve Iribarne MIME-Version: 1.0 To: linux-mtd@lists.infradead.org Subject: bud_replay size question Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi List. We had a problem here in our released product where we would get the dreaded "Error reading superblock!". First some stats: ARM processor (iMX25) U-Boot version (U-Boot 2009.06-rc2-svn3608) <- I know this is autogenerated but what the heck... I still don't know how to reproduce the problem but I know what is causing the issue. The issue is that ubifs_get_sb fails. The reason it fails is that insert_node (u-boot/fs/ubifs/replay.c) runs out of memory. So I can fix the problem by giving u-boot more space for malloc (increase the size of CONFIG_SYS_MALLOC_LEN) This is all fine and dandy but I really don't like updating the bootrom in the field. So I'm trying to get this value correct. I have approx. 58MB to play with here. Our file system lives on a NAND flash that is 256MB total but I have it broken up into 3 partitions. 1 is 10MiB and the other two (the ones that really hold most of the data) have 100MiB each. What I'm trying to determine is how to figure out how big the replay_bud LEB list can get based on my configuration. Is there such a thing or am I just dreaming? Thanks. -stv -- Steve Iribarne Sr. Software Engineer Embedded Devices