this post was submitted on 15 Jul 2024
374 points (96.5% liked)
linuxmemes
21291 readers
936 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Okay, so here's the recap:
I woke up this morning and decided my main drive (just a 500GB SSD) was too full, at about 85%, so I decided to do something about that. I go through the usual:
pacman -Sc
,paccache -rk0
, andpacman -Qqtd | pacman -Rns -
(which I've aliased to "orphankiller" because that's too much typing for me). None of that did anything though, as I'm usually pretty up on this, and I expected it, so my next step was to find other ways of deleting unnecessary files floating around, and that meant a trip to the usually very helpful Arch wiki.On the page "pacman Tips and Tricks", I find 1.7: Detecting More Unneeded Packages. "Perfect!" I thought, "That's exactly what I'm looking for!" I enthusiastically type in the command
pacman -Qqd | pacman -Rns -
, and then quickly go check how much space I just saved. Nada. Or at least not enough to move the percentage point. "Oh well, keep looking," I think and I go back to Firefox to click some more links in hopes that one of them will be the space saving ultra-script that I need. The first one I click, I get an error from my trusty browser, I don't remember exactly what it was but it was something about not being able to verify the page. "Weird, let's try another one." Nope, same thing.Well, being that I had just deleted something, I figured I should go see what exactly it was that I did. It was a good thing I'd left the terminal window open, because after just a few scrolls I saw it:
ca_certificates
, which Firefox absolutely needs. "Great, I'll just reinstall." Nope! I just deleted my pacman cache, and pacman also needs those certificates to download from the Arch repo's mirrors! "Fantastic," I grumbled while I tried to think of how I could get this pesky package back on my machine.Then it occurred to me: I've been keeping up with my btrfs snapshots (for once, lol)! I can just backup to yesterday and forget this whole mess! So I bring up Timeshift, and we're on our way back to a functioning system! Or so I thought. See, I don't have a separate /home partition, but I do have a separate @home subvolume, so when Timeshift asked me if I wanted to restore that too, I clicked the check mark. Only thing is, I don't think I actually have a separate @home subvolume, which brings us to the error in the meme. /home wouldn't mount, and that meant I was borked.
Fortunately, our story has a happy ending! I DDG'd the error on my phone, and found a post from like seven years ago, about someone who had this same set of circumstances, and the one reply was my fix: just go into
/etc/fstab
and delete the "subvolid" part of whatever partition that's giving you grief. Did that, reboot, and we're finally fixed! And now, forevermore, I shall check what I'm deleting before I hit the enter button!The post-script is bittersweet though, because after all this trouble, and then the rest of the afternoon working on the original problem, I am down to... 81%. Oh well.
try qdirstat maybe
That's the second recommendation for qdirstat, so it's definitely on the tomorrow list!
And for cli ncdu is great