[SOLVED] Low space on boot

colorpurple21859 · 04-06-2023, 09:11 AM

what happens if you do this in a terminal:

Code:

sudo umount /home

If the system doesn't lock up requiring a hard power off or says unable to unmount, post the output of the following:

Code:

df -h
cat /etc/fstab

Penstroke4 · 04-06-2023, 08:00 PM

Quote:

Originally Posted by colorpurple21859

what happens if you do this in a terminal:

Code:

sudo umount /home

If the system doesn't lock up requiring a hard power off or says unable to unmount, post the output of the following:

Code:

df -h
cat /etc/fstab

<<<<<<<<<<<<<<<<
Below is the response:-

When I key-in the command " sudo umount /home" .The response is

Code:

sudo umount /home
umount: /home: target is busy.

Code:

df -h
$ cat /etc/fstab

#
# /etc/fstab
# Created by anaconda on Sat Aug 20 08:33:02 2022
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
UUID=1ae30cdf-07b6-4e89-b0f2-7e2ac2a7c4d4 /                       btrfs   subvol=root,compress=zstd:1 0 0
UUID=bfcbd0d0-5e1f-43c6-8d85-1f0fa0a6cae5 /boot                   ext4    defaults        1 2
UUID=1ae30cdf-07b6-4e89-b0f2-7e2ac2a7c4d4 /home                   btrfs   subvol=home,compress=zstd:1 0 0
UUID=ac1205ac-eef2-4534-b75a-6be24364697a none                    swap    defaults        0 0
[Penstroke4]] $

michaelk · 04-06-2023, 08:37 PM

The OP is using btrfs subvolumes and there is nothing wrong with the fstab file. I suspect the warning message is actually for /(root) and not boot. Have you checked the boot logs?

Quote:

/dev/sda9 73G 68G 3.7G 95% /

At the moment I do not know why your system is misbehaving but maybe you have some process that has gone astray. Do you have a backup program running? btrfs snapshots? As suggested can you free up some space?

Penstroke4 · 04-07-2023, 09:05 AM

Quote:

Originally Posted by michaelk

The OP is using btrfs subvolumes and there is nothing wrong with the fstab file. I suspect the warning message is actually for /(root) and not boot. Have you checked the boot logs?

At the moment I do not know why your system is misbehaving but maybe you have some process that has gone astray. Do you have a backup program running? btrfs snapshots? As suggested can you free up some space?

The OP is using btrfs subvolumes and there is nothing wrong with the fstab file. I suspect the warning message is actually for /(root) and not boot. Have you checked the boot logs?

Quote:
/dev/sda9 73G 68G 3.7G 95% /
<<<<,I have tried as suggested but after I have reach /dev/sda9, I see that it is locked (lock icon)I cant open it.
However at this point, i have to inform that on reboot I have tried to use Gnome classic on Xorg desktop - the ethernet connect speed is only 1.2mbps instead of the subscribed speed at 50mbps and constantly lagging & freezing
However after I have switched to Plasma Wayland desktop the speed has increased upto 50++mbps and no lagging or . I am confused by the differences. Does it mean the fault is due unsuitable desktop for my system?

BTW how do I clear for more space? What command to apply?. Thanks

mrmazda · 04-07-2023, 09:13 AM

Quote:

Originally Posted by Penstroke4

BTW how do I clear for more space?

Comment 21 touched on this.

pan64 · 04-07-2023, 09:16 AM

the network issue and the disk space issue are two different things. I would probably open another thread, do not mix both of them here

Penstroke4 · 04-07-2023, 07:02 PM

Quote:

Originally Posted by pan64

hm. That is quite strange, it looks like /dev/sda9 mounted twice (/ and /home are both the same device). That is definitely incorrect, you ought to fix it somehow.

<<<<
With reference to the above "/dev/sda9 mounted twice (/ and /home are both the same device)".
Is this error -still needs to corrected?
Thanks

michaelk · 04-07-2023, 07:23 PM

No, see post #33.

To find biggest files and directories in /home.

du -a /home | sort -n -r | head -n 5

pan64 · 04-08-2023, 05:28 AM

Quote:

Originally Posted by Penstroke4

<<<<
With reference to the above "/dev/sda9 mounted twice (/ and /home are both the same device)".
Is this error -still needs to corrected?
Thanks

No, it is not an error, just we did not know (at least I did not assume) you use btrfs. But we have still two issues, the disk full and network error are probably not related to each other.