search

bluerobotics / BlueOS

The open source platform for ROV, USV, robotic system operation, development, and expansion.
https://blueos.cloud/docs/
Other
140 stars 70 forks source link

BlueOS could be more helpful in showing what is bloating the disk #2572

Open rafaellehmkuhl opened 4 months ago

rafaellehmkuhl commented 4 months ago

I had a situation now where my disk was full. The problem is: what is bloating the disk? My first guess was that it could be the docker images, but removing the three unused ones got me only 8% of the disk back.

Looking at the system information, it has this:

image

We could put more information here, detailing which are the folders that take the most space in the system.

rafaellehmkuhl commented 4 months ago

More info on that: my system has about 3GB of extensions that I do not use anymore and that I have no way to delete besides with the command line.

image
ES-Alexander commented 3 months ago

This is a slightly broader version of #1482. There's some relevant discussion in that issue about how to go about presenting this, and what we'd want it to cover :-)

rafaellehmkuhl commented 3 months ago

Yup. In my case thought (and probably for most people) the images use a lot of space, but they are not the biggest problem.

I suspect there's something on the Docker overlay system being left.

ES-Alexander commented 3 months ago

Quoting from my comment in the other issue:

... it would be preferable if we could also display things like the space taken up by old (still installed) versions, and by data / logs stored in the filesystem (per https://github.com/bluerobotics/BlueOS/issues/1640).

Something like one of these could be useful, although given we want a webUI we might want something like diskover. Alternatively we could roll our own with the specific categories and groupings we're interested in - not sure how involved that would be.

rafaellehmkuhl commented 3 months ago

Found the culprits:

image

Almost 10GB of autopilot logs.