Hi, bhous

I could change rootfs size 230MB to 461MB with following method.
My kernel version is 2.6.39.

1) Modify overo.conf

$ (work_dir)/org.openembedded.dev/conf/machine/overo.conf  

Before: MKUBIFS_ARGS = "-m 2048 -e 129024 -c 1996
After:    MKUBIFS_ARGS = "-m 2048 -e 129024 -c 4044


2) Build kernel

$ bitbake -f -c compile virtual/kernel

$ bitbake virtual/kernel


3) Flash uImage to NAND


I refered this topic.

http://gumstix.8.n6.nabble.com/Gumstix-s-UBIFS-NAND-image-on-Overo-512MB-512MB-tt559107.html


thanks,

---

Jun Y



2012/12/20 bhous <bhouston@lgsinnovations.com>
Hi all,

I've successfully have flashed my overo air via an sd card using both of
these tutorials:
www.gumstix.org/create-a-bootable-microsd-card.html
www.gumstix.org/how-to/70-writing-images-to-flash.html

I'm built the omap3-console-image using the 3.2 image version.
My question is this: After boot up from NAND, why when I run df -h, I have a
rootfs that is half the size of the expected 512MB?
1) I'm thinking it has to do with ubiformat that is called when I run the
overoflash.sh.

2) Or is it how the ubinize is config'd on my Ubuntu development machine?

3) Or is it based on how sudo mke2fs -j -L rootfs /dev/sdb2 is formatting
the second partition?

Maybe it is none of these, but I'm not sure, as this is the first time I've
ever done this kind of thing.


------ snip it -----------
root@overo:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
rootfs                230M  116M  114M  51% /
ubi0:rootfs           230M  116M  114M  51% /
devtmpfs              244M  140K  244M   1% /dev
none                  244M  140K  244M   1% /dev
tmpfs                 244M  328K  243M   1% /var/volatile
tmpfs                 244M     0  244M   0% /dev/shm
tmpfs                 244M     0  244M   0% /media/ram
---------------------------

dmesg
------ snip it ---------
UBI: attaching mtd4 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: max. sequence number:       26
UBI: attached mtd4 to ubi0
UBI: MTD device name:            "rootfs"
UBI: MTD device size:            505 MiB
UBI: number of good PEBs:        4044
UBI: number of bad PEBs:         0
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 4044
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 3/1
UBI: image sequence number:  1305457521
UBI: background thread "ubi_bgt0d" started, PID 49
-------------------------------

Thanks,
Ben






--
View this message in context: http://gumstix.8.n6.nabble.com/Overo-Air-rootfs-disk-space-smaller-than-expected-tp4966293.html
Sent from the Gumstix mailing list archive at Nabble.com.

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users