Is there no easy way to know what is consuming root?
 

Is there no easy way to know what is consuming root?

Re: Is there no easy way to know what is consuming root?
 

There is a App called Storage Usage that displays all applications. Simply press scan packages. Works pretty well. But I think its in Extras Dev so usual warnings apply. It has been pretty stable for me.

Re: Is there no easy way to know what is consuming root?
 

I had it but I find DiskUsage better and faster.. However, both only show total memory usage not what is on root

Re: Is there no easy way to know what is consuming root?
 

Have a look at /usr and /usr/lib folders in the App. You will find most programmes there that are not opt with size of memory usage.

Re: Is there no easy way to know what is consuming root?
 

start terminal, type "sudo gainroot" and then "du -hs *".
also check against "mount" which of those dir are effectively in the same partition as root (/home is big, but isn't).
also "df -k" is handy to know the amount of free/used space in every partition.
Anyway, most of the root space is consumed by /usr, and I wouldn't remove anything from there if I don't know exactly what it is.

Re: Is there no easy way to know what is consuming root?
 

You can also use this script to find the top 50 space hogs

See this thread rootfs full

Re: Is there no easy way to know what is consuming root?
 

I use the attached perl scripts (modified from others posted here) to do this - they'll report all packages using rootfs space, and how much they're using (or how much space a given package is using, in total or per file).

EDIT: I've updated the attachment. The new version now reads the dpkg data files directly instead of calling dpkg (which gives an enormous speedup), and also reports the display name as well as the package name (where available).

EDIT2: I've updated the code again, removing the hardcoded non-rootfs paths and instead using stat to check the device IDs for the rootfs and the filesystem the file is on. This means it will deal with any bind mounts, symlinks, etc. transparently. I've also moved the scripts to my webspace rather than having to keep them updated here. They can now be downloaded from http://www.robinhill.me.uk/maemo/package_sizes.html

Re: Is there no easy way to know what is consuming root?
 

When i follow the instructions i get an error, i think i might be doing it wrong.

I've unzipped the files to a folder in MyDocs called "p"

This is the part i want to run...

so i tried to run it using

but i get an error back...

All i want to do is find out what i've installed thats taking up so much rootfs space. I only have 22mb left withextras-devel and extras-testing disabled. 10mb left when i enable extras-devel.

Re: Is there no easy way to know what is consuming root?
 

You'll need to be in the same directory to run it, so:
It's probably best to output to an ordered file as well, so:
You can then use "more sizes.txt" to read through the file - the largest rootfs users will be at the top.

Re: Is there no easy way to know what is consuming root?
 

ah, i thought i could run it with the path.

also, i think the output to txt helped alot.

Right... here is the contents of the txt file.

My problem now is that the total of those sizes add up to 315820. That converts to just under 308mb. The rootfs file size is only reported as 227.9mb when i do a "df -h" in xterminal.

Also, there only looks like 2 things in that list that i could remove, and thats the PokerTH's which would give me back around 13.5mb. Although, when i installed PokerTH, my rootfs didn't go down by anywhere near 13.5mb.

Is this script showing the rootfs and some other place?