Reply
Thread Tools
javispedro's Avatar
Posts: 2,355 | Thanked: 5,249 times | Joined on Jan 2009 @ Barcelona
#21
Originally Posted by Timo View Post
In my case I had over 50mb free before I tried to update. I had installed packages only from official repos but I still could not update OTA and it asked me to update via PC..
This is interesting. By "official repos" you mean Extras _only_ (not devel or testing)? Do you know what was filling your rootfs?
 
Posts: 4 | Thanked: 0 times | Joined on Dec 2009 @ Espoo, Finland
#22
Originally Posted by javispedro View Post
This is interesting. By "official repos" you mean Extras _only_ (not devel or testing)? Do you know what was filling your rootfs?
Yes, I mean only extras. I have not installed stuff from devel or testing or even activated those repos. Thats why it was a surprise to me that I couldn't update using package manager.

Also It is strange that before update there was only ~35mb free in rootfs. I thought that this was to reason why I couldn't do the update so I tried to free space by reinstall python (that was suggested in some thread). Eventually I managed to get 55mb free but still it didn't allow me to update OTA. I have no idea what was filling my rootfs, now after the update amount of free space is 41.58mb. I hope that next time I can do update using package manager.
 
javispedro's Avatar
Posts: 2,355 | Thanked: 5,249 times | Joined on Jan 2009 @ Barcelona
#23
With 55 MiB it should start the update. Was any package conflicting maybe?
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#24
If it tells you to use NSU then the issue is a conflict (though it would be far better for the tool to display which packages are causing an issue) - if the issue is space on the rootfs then it tells you there's not enough memory in the install location (or something along those lines).
 
Posts: 4 | Thanked: 0 times | Joined on Dec 2009 @ Espoo, Finland
#25
Originally Posted by javispedro View Post
Was any package conflicting maybe?
That is the most likely the reason (but shouldn't happen if only official repos are used). I tried to investigate that before the update but I could't figure which package it was. Package manager didn't tell what was the problem (it just told that update OTA is not possible). If I remember correctly apt-get didn't give any errors, only problem with apt-get was that rootfs ran out of space.
 
Posts: 292 | Thanked: 131 times | Joined on Dec 2009
#26
Originally Posted by wmarone View Post
The speed increase gained by using the OneNAND instead of putting everything on the eMMC and booting off of it is more than worth the issues it causes.
Can you give us some numbers? I'm really curious to see them.

There are some solutions in the Wiki that could compensate from having a slower but larger partition instead of the very limited rootfs. For instance, make some kind of large partition in the eMMC, placing almost everything there. Place only the /boot, some recovery stuff and some of the most speed critical applications (phone?) on some directory mounted on the OneNAND. Those get a symlink from the standard location to the "fast partition".
 
Posts: 292 | Thanked: 131 times | Joined on Dec 2009
#27
Originally Posted by javispedro View Post
"Defect"? I understand you can be a purist and dislike the symlink forest, but I've installed a shitload of nonoptified packages (including Samba and the whole of sunrpc, nfs, samba and inetd) and I still have 58 MiB free. And I didn't delete a single locale...

It was _less than a year ago_ that we were happily using a device with ONLY the 256MiB chip -- no ext3 partition. Though to be fair, heavy data files were usually installed to the FAT32 sdcard, and the base system was smaller.

You shouldn't really be able hit the rootfs limit without installing non-extras-stable packages.
A long time ago, in a galaxy far far away, Bill Gates said that 640KB of RAM would be enough for everybody.

We know that some compromises had to be done. However, I think it is time to discuss how to get it better instead of just keep defending historical decisions.
 
Posts: 93 | Thanked: 30 times | Joined on Sep 2009 @ Sydney, Australia
#28
Realistically, nothing is going to change for Maemo5.

The question is what changes (if any) have been made in Maemo6/Harmattan to fix this problem. If we are still relying on OPTIFY in Maemo6, then that will be a big fail.
 
nicorumiz's Avatar
Posts: 96 | Thanked: 16 times | Joined on Jan 2010 @ Denver, CO -> Italy
#29
Originally Posted by Zelig87 View Post
Realistically, nothing is going to change for Maemo5.

The question is what changes (if any) have been made in Maemo6/Harmattan to fix this problem. If we are still relying on OPTIFY in Maemo6, then that will be a big fail.
If nothing is going to change will be a big problem for the future....what we are supposed to do, change phone every year?

I have 11 apps installed (Irreco, SNES, Airport, Angry Birds, Irreco, Gonvert, Level, Petrovich, Fm radio, VNC, Wiicontrol) and I have less then 50MB free on rootfs....I know, few of them are not optimized...This rootfs is a big fail I think, they should make 2GB for rootfs and 10GB for Apps(or make those 10 customizable by the user).
 
Posts: 21 | Thanked: 0 times | Joined on Dec 2009
#30
One thing I have noticed, is that rootfs' free space fluctuates throughout the normal operation of the device. When I turn it on now, I have 70mb free. After a couple hours to a day, this is 50mb free. As I turn my phone off at night before I sleep to avoid anyone calling me, I'm not sure how bad this gets after a week of 'uptime'. Is it 'safe' to move all of /var to the opt partition? I'm assuming this is where the space usage is coming from but haven't done any real investigation yet... I guess /var is needed during bootup before /opt is mounted however..
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 18:16.