Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.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.
I'll give the whole story if anyone wants it
This is an interesting read, even if it is a few years old https://arstechnica.com/gadgets/2021/09/examining-btrfs-linuxs-perpetually-half-finished-filesystem/
I gave up on it in in 2016 and it sounded all the same back then too with too many people giving it a pass for unacceptable behavior. I don't think anything has really changed since.
Interesting, I'll keep that in mind for if I go for a RAID setup, but for now it's just my one drive on BTRFS, the other one is ext4.
sound's like timeshift's fault, not btrfs
Could be, seems to me that BTRFS didn't match the subvolid between @home and what it expected @home to be in the fstab, but I won't claim to be an expert lol
I've been burned by btrfs before. Never again. It's not a good file system, especially for multi disk systems.
I've had two production systems fail because btrfs didn't balance metadata and file space like it says it will. It has some fancy features, but do you need them?
Idk about all that, it's been fine for me, just a little misconfiguration here. The compression just saved me a bunch of storage space, so I'm kinda in btrfs' corner right now lol
It was fine for me too, right up to the point that it really wasn't.
I don't understand why people use Arch. It takes all kinds I suppose. For me I automate everything and use preconfigured stuff when I can.
I like to tinker, plus I can be absolutely assured that every problem with my system is 100% my fault, which actually makes it easier to track down any problems. But the main reasons people use Arch is probably the rolling release model and the AUR.
It isn't necessarily your fault as it is unstable software. It is going to break and fall apart. I feel like having a homelab is a much more productive way to tinker.
Arch isn't unstable, I just keep breaking things in my ignorance. The only thing in this scenario I could pin on Arch is that the "ca-certificates" package should have been marked as a dependency for pacman, but I guess it's not strictly a dependency, as you can use pacman to install stuff from a local repo. Definitely for Firefox, though, as you can not browse the internet without the certs.
Yup, only reason I can't move on is because of the AUR and the rolling release, though, having said that I'm thinking of trying NixOS but not quite sure it's for me as it isn't posix. It seems some software doesn't really like that although I've heard it's pretty awesome as a server OS.
Yeah, I could see it being a good server OS, but otherwise NixOS seems like it's on the "immutable" thing that's popular right now. I've tried a few immutable distros, and they're not for me, I end up layering everything anyways lol
Yhea, that's my though. I wanna keep up to date and quite frequently change my system. I like having the reproducibility but feel like the immutable might get in the way. My servers though stay pretty static.
Just an update: following the very helpful suggestions in this thread has gotten my drive usage down to 16%! Super happy about that, y'all rock!
My moment was using the experimental repos to get an early view into wayland, after seeing it wasn't quite ready for my system I just switched back. Mistakes made, and slowly over the next few weeks as I updated, the experimental packages never got superseded and updated, until my system crashed and would not pass boot.
Luckily since it is not windows I just used a live usb stick to mount the disk and manually reinstall all the broken system packages. Scary but made me feel pretty confident I could recover the system myself in the future. Also learned a pretty important lesson. Don't do that, and look at the upgrade log if you do lol, cause the whole time, as I upgraded there was red text showing me all the system packages that were not getting updated.
After fixing some Windows problems with their version of a live USB (the recovery USB) I really don't want to do it ever again. It's harrowing.
Sometimes, when it backstabs me, I call it BeTRayFS
I use qdirstat a lot to determine what files are eating all my space
I will check that out! Mostly I've been looking for something to determine what files are no longer in use, like old configs for programs I don't even have anymore, etc.
I think pacreport --unowned-files might be able to help with that too. Showing you files that aren't part of any installed package. Probably only does system files though, nothing in /home