hello,
I know there are lots of rootfs full threads. but my problem is different: I get messages that the rootfs is full but I have 80MB left.
Why do I get those messages? I can't get new IM, emails or make browser bookmarks.

Some error messages are just guesses about what the problem might be. When I get a message that doesn't make sense, I figure it really means 'hey dude, something ain't right.'

Mostly with this kind of thing it is something like a broken package.

Please check the output of for infos regarding your issues.
Feel free to ask if still questions arise.

thanks for your quick replies. i noticed that the errors are gone since the phone was rebooted. my device was flashed about a week ago. rootfs was mount rw, i thought about filesystem errors or bad blocks. since the last reboot everything is ok. i hope for a long time..

the outputs of what michaaa sugested:

~ $ df -h
Filesystem Size Used Available Use% Mounted on
rootfs 227.9M 145.3M 78.4M 65% /
ubi0:rootfs 227.9M 145.3M 78.4M 65% /
tmpfs 1.0M 76.0k 948.0k 7% /tmp
tmpfs 256.0k 92.0k 164.0k 36% /var/run
none 10.0M 72.0k 9.9M 1% /dev
tmpfs 64.0M 4.0k 64.0M 0% /dev/shm
/dev/mmcblk0p2 2.0G 282.9M 1.6G 15% /home
/home/opt 2.0G 282.9M 1.6G 15% /opt
/opt/pymaemo/usr/lib/python2.5
2.0G 282.9M 1.6G 15% /usr/lib/python2.5
/opt/pymaemo/usr/share/pyshared
2.0G 282.9M 1.6G 15% /usr/share/pyshared
/opt/pymaemo/usr/lib/pyshared
2.0G 282.9M 1.6G 15% /usr/lib/pyshared
/opt/pymaemo/usr/share/python-support
2.0G 282.9M 1.6G 15% /usr/share/python-support
/opt/pymaemo/usr/lib/python-support
2.0G 282.9M 1.6G 15% /usr/lib/python-support
/dev/mmcblk0p1 27.0G 874.2M 26.1G 3% /home/user/MyDocs


~ $ mount
rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,bulk_read,no_chk_data_crc)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /tmp type tmpfs (rw,noatime,size=1024k)
tmpfs on /var/run type tmpfs (rw,nosuid,noatime,size=256k,mode=755)
none on /dev type tmpfs (rw,noatime,size=10240k,mode=755)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noatime,size=65536k)
/dev/mmcblk0p2 on /home type ext3 (rw,noatime,errors=continue,commit=1,data=writebac k)
/home/opt on /opt type none (bind)
nodev on /sys/kernel/debug type debugfs (0)
/opt/pymaemo/usr/lib/python2.5 on /usr/lib/python2.5 type bind (bind)
/opt/pymaemo/usr/share/pyshared on /usr/share/pyshared type bind (bind)
/opt/pymaemo/usr/lib/pyshared on /usr/lib/pyshared type bind (bind)
/opt/pymaemo/usr/share/python-support on /usr/share/python-support type bind (bind)
/opt/pymaemo/usr/lib/python-support on /usr/lib/python-support type bind (bind)
/dev/mmcblk0p1 on /home/user/MyDocs type vfat (rw,noauto,nodev,noexec,nosuid,noatime,nodiratime, utf8,uid=29999,shortname=mixed,dmask=000,fmask=013 3,rodir)


dpkg --configure -a as root has no output.

hi,
my n900 gives a similar answer.
rootfs: 93.3MB available, use: 58%

but i cannot install an update with less than 450kB. Is says that there is not enough space and that I should delete some software.
even uninstalling software with more then 450k doesnt let me install this update.

Why do "tmpfs"-directories exist?
i've got 3 of them and their space available is
932k, 168k and 64M.
all other directories have at least more space then 9MB.

I uploaded the complete screenshot from my answers.


I read a lot of posts to this topic but most of them explain how to get more space. But obviously I do have enough. So why doesn't my device want to update the software?

I thank everyone in advance thinking about an answer.
I dont want to change to another operating system but this thing drives me crazy.

bye
Markus

Did you check the logs for your application manager? Which application manager do you use? Are you using the community seamless software update (CSSU) packages? Do you have rootsh installed to let apt-get put out some useful error code?

Hi Markus,
I didn't find an answer yet, but since the last time I flashed my device, the problem seems solved. I don't remember exactly, but if the message showed up once more at all after flashing the device, a simple reboot helped.
Still a weird bug. I think it has something to do with filesystem errors and I don't recommend trying fsck or auto fsck at boot (with power kernel), because that's how I screwed up my device totally and why I had to flash it.
Maybe the best thing you can do is (skip the total screw up procedure ) backup everything and do a firmware flash.

Greets,
Simon

Hi,

Me,too get an out of space error though I had 50megs free in my rootfs??

I checked the directory

/var/cache/apt/archives

This directory should be empty. Or it could be empty because it is in /var/cache...
In my case I often install via apt-get and it seems that apt-get leaves a package copy there after each install.
But I'm not 100 procent sure if this is the reason.


After I removed all the deps in the directory above everything was ok.

Give it a try.

asys3

I've just run into bug 7257 and it seems there is a relation between that and this.

First, remove debris from uninstalled programmes using dpkg, as described in the wiki's clear up rootfs page. I suggest by name, rather than the automatic means, incase you remove something you later rely on.

Now for the bit I just found. Even if you don't have a UI file manager, you can still see what might be the problem, using good ol' microB:

1. Go to root directory and ensure you can see hidden files.
2. Look for files that really don't belong there.
3. Open terminal, and as 'root', rm the files you want to remove (for new users - copy & paste in the terminal needs to be done via the menu bar so you can take file names from the browser screen)

In my case, I found that get_iplayer had deposited a download in the /root folder so the whole system got clogged up.

If you can't decide whether something should be there or not, well, that's when to ask for help!