I assume that “/dev/sdb2” is the root partition. At 24.6G, that’s a bit tight, especially with Tumbleweed. Are you using “btrfs” or some other file system?
Is “/tmp” a directory under root, or is it mounted as “tmpfs”?
If it is a regular directory, look for files there that can be deleted to clear up space.
Otherwise look at “/var/log”. As a quick fix you can try:
cd /var/log
rm *.xz
Those are archived old log files, and removing them might clear up a bunch of space.
From your newer posts I conclude you are mutilating the excellent performance of Tumbleweed on AMD Ryzen 5 2600 / AsRock B450M Pro4 by the following:
Using Hard disks which is PITA. Get a NVMe 4x SSD instead: Any brand will be fine. As a reference use SAMSUNG 970 EVO Plus SSD 2TB - M.2 NVMe Interface
ignoring disk space problems. Increase partition size and watch for UNALLOCATED space:
**erlangen:~ #** btrfs filesystem usage -T /
Overall:
Device size: 51.69GiB
Device allocated: 42.04GiB
** Device unallocated: 9.65GiB **
Device missing: 0.00B
Used: 32.37GiB
Free (estimated): 17.64GiB (min: 17.64GiB)
Free (statfs, df): 17.64GiB
Data ratio: 1.00
Metadata ratio: 1.00
Global reserve: 100.61MiB (used: 0.00B)
Multiple profiles: no
Data Metadata System
Id Path single single single Unallocated
-- -------------- -------- -------- -------- -----------
1 /dev/nvme0n1p3 39.01GiB 3.00GiB 32.00MiB 9.65GiB
-- -------------- -------- -------- -------- -----------
Total 39.01GiB 3.00GiB 32.00MiB 9.65GiB
Used 31.01GiB 1.36GiB 16.00KiB
**erlangen:~ #**
You did not tell us to which Tumbleweed version you were updating. However if you updated to 20210920 probably most of your system was updated.
On my system zypper is configured to first download all new packages to its cache and the install them (that might be the default setting). In my case that were approximately 3000 packages which had to be cached.
If your root filesystem is only 24 GiB then that could become a problem. You have several options to avoid this
Increase the size of your root file system (40 GiB with ext4
, probably more with btrfs an snapshots enabled). - Move your zypper
cache to a device with sufficient space (e.g. i keep my zypper cache on my NAS). - Do not install recommended packages (e.g. my system takes 14 GiB with plasma5 as DE).
[QUOTE=karlmistelberger;3068637]From your newer posts I conclude you are mutilating the excellent performance of Tumbleweed on AMD Ryzen 5 2600 / AsRock B450M Pro4 by the following:
Using Hard disks which is PITA. Get a NVMe 4x SSD instead: Any brand will be fine. As a reference use SAMSUNG 970 EVO Plus SSD 2TB - M.2 NVMe Interface
ignoring disk space problems. Increase partition size and watch for UNALLOCATED space:
If you send me 250 euro I will This reminds me why I went for two harddisk.
I have been thinking of getting an ssd for tumbleweed though.
That freed up some space but , I still get the warning, it now says 130 Mib left
I am using ext 4, but not sure about the root partition. That might be xfs ?
Do I need to go into YAST, and make my home dir smaller, then add that free space to my root partition ?
Your setup is very reasonable apart from the HDDs. You may add a smaller disk: https://www.idealo.de/preisvergleich/OffersOfProduct/6446461_-970-evo-plus-samsung.html I am fine with 512 GB on NMVe. Even a Crucial CT250MX500SSD1 holding system and heavily used /home files will boost performance and ease maintenance significantly. Prices start at 38 €.
Changing drive types will not solve space problems on root. Faster drives are nice but do not fix space miss-allocation.
If your home partition is XFS you can not reduce its size. XFS problem. Be certain on how all partitions are formatted before proceeding. Also you must reduce home and then move it to allow space for root to expand into.
Its been a while since I build this pc, but I clearly messed something up. Home should have been ext 4. (that was what i wanted, but clearly made a mistake)
Now how do I fix this mess?
I need to do a fresh install of tumbleweed ?
Wondering if I can copy my home to the windows disk ? In theory that should fit ?
Why do you want to change the file system of /home from xfs into ext4? What is the problem?
When you really want this, you should off-load the data (which is not more then an extra backup), create a new ext4 file system on the partition and restore the data.
I would like to expand the root partition, because it seems to be small.
To do this I need to shrink the home partition, and that seems to be a problem with xfs.
If there is a better solution, to free up more space in root, I would love to hear it.
Currently root has 4 gig free space, out of 24.1 gig. I made some progress, with help of this topic.
How would I create an back up ? If its compressed I might be able to park that back up, on the windows disk ? (both hard disk in my pc are 1 gig)
Normally 24 Gb should be more then enough for an ext4 / file system. If you can not explain the space used by excessive installing software, then go and search. It is more instinct then real science.
You friend is of course
du -sh
or, when inside a directory
du -sh *
Is /tmp a separate file system? When not check what is in there.
cd /tmp
du -sh *
Also logs can grow.
As a last resort serach from the root:
cd /
du -sh *
when you see something very large then step to it and go on:
I will see what I can find. The list of extra software, I probably know from the top of my head. LMMS,Carla, Audacity, QMMP, Blender, Mplayer, VLC, a Virtual machine, chrome and MAME. (I might forget a few I don’t use often)
I do wonder if that virtual machine is causing this, but that’s a gut feeling, which I can’t back up (yet? ) .