this post was submitted on 29 Oct 2023
1 points (100.0% liked)

Linux

48323 readers
638 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

Dust is a rewrite of du (in rust obviously) that visualizes your directory tree and what percentage each file takes up. But it only prints as many files fit in your terminal height, so you see only the largest files. It's been a better experience that du, which isn't always easy to navigate to find big files (or atleast I'm not good at it.)

Anyway, found a log file at .local/state/nvim/log that was 70gb. I deleted it. Hope it doesn't bite me. Been pushing around 95% of disk space for a while so this was a huge win 👍

top 6 comments
sorted by: hot top controversial new old
[–] anagram3k@lemmy.ml 0 points 1 year ago (1 children)

ncdu is the best utility for this type of thing. I use it all the time.

[–] dan@upvote.au 1 points 1 year ago* (last edited 1 year ago)

Try dua. It's like ncdu but uses multiple threads so it's a lot faster., especially on SSDs.

[–] netchami@sh.itjust.works 0 points 1 year ago (2 children)

I think something might be wrong with your Neovim if it aggregated 70 gigs of log files.

[–] Aatube@kbin.social 2 points 1 year ago

don't worry, they've just been using neovim for 700 years, it'll be alright

[–] nik282000@lemmy.ca 1 points 1 year ago (1 children)

So I found out that qbittorrent generates errors in a log whenever it tries to write to a disk that is full...

Everytime my disk was full I would clear out some old torrents, then all the pending log entries would write and the disk would be full again. The log was well over 50gb by the time I figured out that i'm an idiot. Hooray for having dedicated machines.

[–] netchami@sh.itjust.works 1 points 1 year ago

I once did something even dumber. When I was new to Linux and the CLI, I added a recursive line to my shell config that would add it self to the shell config. So I pretty much had exponential growth of my shell config and my shell would take ~20 seconds to start up before I found the broken code snippet.