Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] - Disk management #1989

Open
Fredo-Ronan opened this issue Sep 6, 2024 · 1 comment
Open

[Feature request] - Disk management #1989

Fredo-Ronan opened this issue Sep 6, 2024 · 1 comment

Comments

@Fredo-Ronan
Copy link

Fredo-Ronan commented Sep 6, 2024

Is your feature request related to a problem? Please describe.
I tried installing custom app through the import docker-compose.yaml file feature but it fails on the way of downloading some dependencies and take a lot of storage in my sdcard, i just want a way to find the kind of temp files that already downloaded when the installation was in progress

Describe the solution you'd like
I would like the ability to access the sdcard in root privilege or sort of disk management feature on windows system to see easily what is the thing that taking up so much space on storage and delete it safely without damaging the other main filesystem

Describe alternatives you've considered
I tried using the native file manager that CasaOS has and change the view to list in order to see the file size, but the size doesn't appear if the file is in the root OS system

Additional context

  • My CasaOS installation is on top of Armbian Linux system (Armbian_21.08.1_Amlogic-GXL_bullseye_current_5.10.60)

Here you can see the main storage is taking up space to 7 GB of 14GB total storage capacity
image

And here you can see the thing that taking up so much space is the /dev/mmcb1k2
image

But on the file browser, the size indicator says 0 bytes
image

@georgerappel
Copy link

I thi k you are misunderstanding some things here.

That path /dev/mmcblk1p2 is the filesystem path of the mountpoint "/", as you see ok the first screen, which is your OS root path. This is where all of your operating system files are. If you do anything to that file or the root path, you might end up with a corrupted OS. I don't know why it has 0bytes, maybe it's a symlink, but it's outside of my knowledge how all that works under the hood.

I wouldn't change the size of it either, as if you limit the size of this partition you could end up with more problems, unable to boot, unable to update dependencies or the OS, unable to install more software etc.

I highly suggest you learn how the mount points and the filesystem paths for them work before trying to do anything with system files manually.

If you need to free disk space, maybe try command line commands to clear cache of downloaded apps, or just leave it alone while you learn your way through Linux.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants