To note, gecko/gaia takes roughly about 101 MB for the flame device. Depending on how you flash, OTA ( which requires twice that space) or partial FOTA which requires that space + the largest sized file from the zip at bare minimum. OTA unzips the files from the zip file and swaps the files while the system is hot (up). It creates a backup file of each of the files and thus requires twice as much space as the size of the OTA. FOTA unzips a file at a time and replaces the file and then moves on to the next. At least that's how it was explained to me when I was digging into things and talking to the Devs. OTA won't work for the flame if 149 MB of space is available. That's why we switched to FOTA.
Just a fyi : I can't recall for the flame, I do recall a bug with the Alcatel devices where storage space on the devices won't recover if you delete something until you reboot the device. Hamachi/Buri devices used to run into these issues often during our python marionette runs in which I helped sdonner troubleshoot. On Tue, Jan 12, 2016 at 8:38 AM, <[email protected]> wrote: > Le mardi 12 janvier 2016 11:43:57 UTC+1, Alexandre Lissy a écrit : > > > > Spread accross ?! It makes no sense. Can you share more details? > > Well... yes... spread across, if my English > > Since I've just updated (manually mimicking shallow-flash.sh tool) my Fire > E device to FxOS 2.1 using latest Flame KK device v2.1 Gecko/Gaia, this is > even cleaner than I thought. > > Now the details. > > On Fire E device, custpack partition mainly holds Gaia: > > emeric@ubuntu:~$ ls -l /custpack > total 28 > drwxr-xr-x. 3 root root 4096 avril 14 1970 b2g > -rw-r--r--. 1 root root 5696 avril 14 1970 build.prop > -rw-r--r--. 1 root root 13 août 1 2008 custpack.ver > drwxr-xr-x. 2 root root 4096 juil. 31 2014 libs > drwx------. 2 root root 4096 janv. 1 1970 lost+found > drwxr-xr-x 35 root root 4096 janv. 12 12:52 webapps > > As you can see below, there's still plenty of space left on this partition: > > emeric@ubuntu:~$ df /custpack > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/loop0 197472 51524 141852 27% /custpack > > Still on Fire E device, system partition holds Gecko and B2G, with > symlinks to custpack for files that normally reside on system partition on > other FxOS devices: > > emeric@ubuntu:~$ ls -l /system > total 1220 > drwxr-xr-x. 4 root root 4096 janv. 12 13:06 b2g > drwxr-xr-x. 2 root 2000 8192 avril 14 1970 bin > lrw-r--r--. 1 root root 20 juil. 31 2014 build.prop -> > /custpack/build.prop > drwxr-xr-x. 14 root root 4096 avril 14 1970 etc > drwxr-xr-x. 2 root root 4096 janv. 12 13:12 fonts > drwxr-xr-x. 10 root root 8192 avril 14 1970 lib > drwx------. 2 root root 4096 janv. 1 1970 lost+found > -rw-r--r--. 1 root root 1193947 août 1 2008 recovery-from-boot.p > -rw-r--r--. 1 root root 13 août 1 2008 system.ver > drwxr-xr-x. 3 root root 4096 juil. 31 2014 tts > drwxr-xr-x. 7 root root 4096 juil. 31 2014 usr > drwxr-xr-x. 4 root 2000 4096 avril 14 1970 vendor > drwxr-xr-x. 2 root 2000 4096 avril 14 1970 xbin > > Looking deeper in this partition, you can see other examples of symlinks > to files/folders in custpack partition, such as: > > emeric@ubuntu:~$ ls -l /system/b2g > total 36408 > -rw-r--r--. 1 root root 561 janv. 12 13:06 application.ini > -rwxrwxr-x. 1 root root 112012 janv. 12 13:06 b2g > -rw-r--r-- 1 root root 40 janv. 12 13:06 chrome.manifest > drwxr-xr-x 2 root root 4096 janv. 12 13:06 components > -rw-r--r--. 1 root root 4003 janv. 12 13:06 crashreporter.ini > lrw-r--r--. 1 root root 22 juil. 31 2014 defaults -> > /custpack/b2g/defaults > -rw-r--r--. 1 root root 52 janv. 12 13:06 dependentlibs.list > drwxr-xr-x. 2 root root 4096 avril 14 1970 dictionaries > -rw-r--r--. 1 root root 218468 janv. 12 13:06 libfreebl3.so > -rw-r--r--. 1 root root 349592 janv. 12 13:06 libmozglue.so > -rw-r--r-- 1 root root 29908 janv. 12 13:06 libmozsandbox.so > -rw-r--r--. 1 root root 1340008 janv. 12 13:06 libnss3.so > -rw-r--r--. 1 root root 444348 janv. 12 13:06 libnssckbi.so > -rw-r--r--. 1 root root 128888 janv. 12 13:06 libsoftokn3.so > -rw-r--r--. 1 root root 28478952 janv. 12 13:06 libxul.so > -rw-r--r--. 1 root root 6006838 janv. 12 13:06 omni.ja > -rw-r--r--. 1 root root 139 janv. 12 13:06 platform.ini > -rwxrwxr-x. 1 root root 5292 janv. 12 13:06 plugin-container > -rw-r--r--. 1 root root 624 janv. 12 13:06 precomplete > -rw-r--r--. 1 root root 275 janv. 12 13:06 removed-files > -rw-r--r--. 1 root root 8915 janv. 12 13:06 run-mozilla.sh > -rw-r--r--. 1 root root 825 janv. 12 13:06 Throbber-small.gif > -rw-r--r--. 1 root root 2895 janv. 12 13:06 ua-update.json > -rwxrwxr-x. 1 root root 82372 janv. 12 13:06 updater > lrw-r--r--. 1 root root 21 juil. 31 2014 user.js -> > /custpack/b2g/user.js > lrw-r--r--. 1 root root 17 juil. 31 2014 webapps -> > /custpack/webapps > > Here again, partition is barely used, roughly half the size: > > emeric@ubuntu:~$ df /system > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/loop0 357080 199844 149864 58% /system > > So, does it now make sense? ;-) > > Hence my original question for Flame device: if it also follows the same > partition layout, the total amount of space accounting for both custpack > and system partitions is probably bigger than the mere empty spaces that > were recovered here and there to increase the size of system partition. Or > not ;-) > > Émeric > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
