Bad partition size on apalis T30 during system upload

Dear Sir,
Im trying to upload linux system on apalis T30 using Apalis_T30_LinuxImageV2.6 with my custom rootfs. I have already changed EMMC_SIZE to: **EMMC_SIZE=$(expr 1024 \* 7450 \* 2 \* 2)** The problem which Im facing is that system is not probably loading completely. After runnig script I can see as follows:

Creating MBR file and do the partitioning
0+0 records in
0+0 records out
0 bytes copied, 0,000119793 s, 0,0 kB/s
Model:  (file)
Disk /home/kamil/apalis/debian_wheezy/apalis-t30_bin/mbr.bin: 30515200s
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End        Size       Type     File system  Flags
 1      8192s   40959s     32768s     primary               lba
 2      40960s  30474239s  30433280s  primary

Creating VFAT partition image with the kernel
mkfs.fat 3.0.28 (2015-05-16)
mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows

Creating rootfs partition image
2758+0 records in
2758+0 records out
2891972608 bytes (2,9 GB, 2,7 GiB) copied, 4,21305 s, 686 MB/s
mke2fs 1.42.13 (17-May-2015)
Discarding device blocks: done                            
Creating filesystem with 706048 4k blocks and 176704 inodes
Filesystem UUID: e3d8ad85-3e5b-4bcb-921c-1a37bce30068
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912

but after system is loaded The final partition is to small:

rootfs          2,5G  2,4G     0 100% /
/dev/root       2,5G  2,4G     0 100% /
devtmpfs        997M     0  997M   0% /dev
tmpfs           200M  212K  200M   1% /run
tmpfs           5,0M     0  5,0M   0% /run/lock
tmpfs           399M     0  399M   0% /run/shm
tmpfs           399M  4,0K  399M   1% /tmp

How can I increase the rootfs partition on Apalis T30 before system copy?

I suspect that you are one of those customers trying to pre-load a huge root file system (whatever the reason for that may be). We actually did integrate this as part of our V2.7 beta 1 release with this, this and this and you may find more information about what exactly got changed in resp. git logs.

Dear Marcel,

My system is approx 2,5 GB so still below the limit. I made few tests end figured it out that setting up MIN_PARTITION_FREE_SIZE=600 resolving the problem. Don`t even have to change EMMC_SIZE.

Dear Kamil

Glad you got this sorted. Yes up to around 4 GB in size you should be fine. Beyond that you may need the fixes from our latest BSP.