33
all 35 comments
sorted by: hot top new old
[-] unexposedhazard@discuss.tchncs.de 14 points 2 years ago

Maybe you have a swap file that happens to be 16GB ?

[-] ColdWater@lemmy.ca 5 points 2 years ago* (last edited 2 years ago)

I only allowed 4G for swap, maybe arch enabled zram and it used 8GB by default and I actually don't need to create a swap partition?

[-] superkret@feddit.org 10 points 2 years ago

Arch doesn't really do anything you don't tell it to do during installation.
That's the entire point. After installing Arch, you know what your system does, cause you configured it.

[-] Kalcifer@sh.itjust.works 12 points 2 years ago* (last edited 2 years ago)

You can try using # du -h -d 1 / to locate the largest directory under /. Once you've located the largest directory, replace / with that directory. Repeat that until you find the culprit (if there is a single large directory).

EDIT (2024-07-22T19:34Z): As suggested by @DarkThoughts@fedia.io, you can also use a program like Filelight, which provides a visual and more comprehensive breakdown of the sizes of directories.

[-] DarkThoughts@fedia.io 15 points 2 years ago

You can use Filelight which is much simpler and more visual.

[-] ByteOnBikes@slrpnk.net 13 points 2 years ago

But it doesn't make you feel like hackerman

[-] SidewaysHighways@lemmy.world 5 points 2 years ago

goddamn does it ever feel good to feel like a hackerman

[-] Kalcifer@sh.itjust.works 2 points 2 years ago
[-] FlexibleToast@lemmy.world 2 points 2 years ago

Df does that too, or did you mean du?

[-] Kalcifer@sh.itjust.works 4 points 2 years ago* (last edited 2 years ago)

Whoops! You are correct — I have updated the original comment. I'm not sure why I wrote df instead of du. This is a good example of why one should always be wary of blindly copying commands 😜 It begins to teeter on being potentially disastrous if I had instead wrote dd.

[-] FlexibleToast@lemmy.world 3 points 2 years ago

Luckily the syntax wouldn't have worked if it was dd

[-] ColdWater@lemmy.ca 2 points 2 years ago

You're a life saver I finally found the culprit

[-] flambonkscious@sh.itjust.works 5 points 2 years ago

Do tell! We need a follow up :)

[-] ColdWater@lemmy.ca 3 points 2 years ago

It's "Steam" inside .local eat up 6GB even though I have not open it yet and tmp files (almost 5GB) that is not clear itself after installing the OS

[-] 0xDREADBEEF@programming.dev 1 points 2 years ago* (last edited 2 years ago)

A fresh Arch install included Steam? Or was this not a fresh install?

[-] ColdWater@lemmy.ca 3 points 2 years ago

I install it during pacstrap

[-] 0xDREADBEEF@programming.dev 2 points 2 years ago

Ah, I see. Just be aware that any additional file size when you get to the stage you can install KDE is pretty much considered the "bloat" part of installs, meaning you only make arch as bloated as you want after that. I like filelight in KDE https://apps.kde.org/filelight/

[-] Artyom@lemm.ee 1 points 2 years ago* (last edited 2 years ago)

Or you could use baobab to do the same thing if you want an answer within 10 minutes.

[-] sunstoned@lemmus.org 2 points 2 years ago

Or dust if you want it fastest with a pretty graph

[-] Potatisen@lemmy.world 9 points 2 years ago

It might have something to do with the dolphin you're keeping in there.

[-] ColdWater@lemmy.ca 3 points 2 years ago
[-] wreckedcarzz@lemmy.world 10 points 2 years ago
[-] radivojevic@discuss.online 5 points 2 years ago

But they’re faster than lightning.

[-] Kalcifer@sh.itjust.works 6 points 2 years ago* (last edited 2 years ago)

Try the following command to list all installed packages sorted by size [source]:

LC_ALL=C.UTF-8 pacman -Qi | awk '/^Name/{name=$3} /^Installed Size/{print $4$5, name}' | LC_ALL=C.UTF-8 sort -h

There may be some unexpectedly large packages installed.

[-] remram@lemmy.ml 5 points 2 years ago

Keep in mind that a part of the filesystem will be reserved on creation. Here if I create a completely empty ext4 filesystem with:

truncate -s 230G /tmp/img
mkfs.ext4 /tmp/img
mount /tmp/img /mnt

Dolphin reports "213.8 GiB free of 225.3 GiB (5% used)"

screenshot

[-] Dirk@lemmy.ml 4 points 2 years ago

Try running pacman -Scc to get rid of the pacman cache.

Also: How did you install KDE?

[-] ColdWater@lemmy.ca 4 points 2 years ago* (last edited 2 years ago)

I used "sudo pacman -S plasma sddm"

[-] Fijxu@programming.dev 4 points 2 years ago
[-] EddyBot@discuss.tchncs.de 3 points 2 years ago

sounds ok for me if you install the full KDE Plasma + all applications package group and add some basic software like LibreOffice

[-] ColdWater@lemmy.ca 3 points 2 years ago

I used minimal plasma (pacman -S plasma)

[-] sanpo@sopuli.xyz 11 points 2 years ago

plasma-desktop is the minimal one.

[-] LinearArray@programming.dev 1 points 2 years ago

use plasma-desktop, that's the actual minimal one.

this post was submitted on 22 Jul 2024
33 points (90.2% liked)

linux4noobs

4413 readers
1 users here now

linux4noobs


Noob Friendly, Expert Enabling

Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.


Seeking Support?

Community Rules

founded 3 years ago
MODERATORS