Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
In the end I reformatted and installed a fresh copy of OpenSuse 15.3. I gave btrfs the benefit of the doubt by again configuring my root filesystem to us it. But this time with a larger partition size of 60GB. I'm now kicking myself.... as I'm back with the same issue and our business server is down.
'snapper list' gives me
Code:
The config 'root' does not exist. Likely snapper is not configured.
See 'man snapper' for further instructions.
Thus, I'm guessing I'm not using snapper and shouldn't have the problem of snapshot files consuming space.
I've heard about the BTRFS huge metadata allocation issue, but I have no idea how to resolve it. Unfortunately, I'm just the user of a btrfs filesystem and far from an expert.
It seems daft to me that this is the second time in less than a year my btrfs filesystem has done this. There MUST be a way to fix it, free up space and prevent any future recurrence? BTRFS from my understanding is a common filesystem, so either everyone has this issue, or I've made a fundamental mistake when configuring mine (both times).
Any help is appreciated, I really don't want to re-install again (if I do, this time in ext4).
Something tells me this will soon fill up due to exactly the same reasons
Probably; 60GB when you have a LOT of disk space to play with seems odd. Have you looked in /var and /tmp?? Log files and journal files can get fairly big, and if you have run updates, you've got several kernels installed too.
Run "rpm -qa | grep -i kernel", and see what's installed. Then run "uname -a" to get the current running kernel...you should be able to remove the older kernels (and kernel development headers, too, if installed), to gain more room. You can also try "zypper purge-kernels" to trim things down, if you do find several older kernels installed.
As a stopgap measure, you may want to symlink /var/log off to one of your larger volumes, but that'd be a last resort for me. Personally, I'd copy everything from /home to /big, reinstall everything (and resizing the root volume on sda3) to be something more along the lines of 250GB, and resize /home accordingly. Don't format /big, of course, and just copy things back to /home when you're done.
I've run 'rpm --rebuilddb' and 'zypper clean --all' with no drastic effect. Is there an obvious way to check snapshots is not enabled?
So far, there's nothing to point to heavy disk usage by a particular file or directory. I don't understand how I can resolve this apart from reinstalling and using an ext4 filesystem.
How do I go about safely removing these kernels? I'm running
Code:
5.3.18-59.5-default #1 SMP Wed Jun 2 08:21:36 UTC 2021 (eaf040d) x86_64 x86_64 x86_64 GNU/Linux
If you look at the packages, you have ONE kernel installed...the one you're using. The others are firmware and other associated kernel files for your system.
So far, there's nothing to point to heavy disk usage by a particular file or directory. I don't understand how I can resolve this apart from reinstalling and using an ext4 filesystem.
You may have update packages remaining; "sudo zypper clean --all" should remove the already-installed update packages (if any), and clear the cache. Beyond that, you're going to have to look to see what's taking up space. SOMETHING is...start with /root, and start traversing things. Lots of suggestions on how to do it, but running:
Code:
sudo du -a / | sort -n -r | head -n 5
...will do it. It will take a while to run, though.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
