Solved 100% storage in MX linux after install sway

[lazy_lain]

i think the title is bad so i will edit it soon

so when i try to setup wayland in my second distro (20gb storage) first i tried labwc and when i entered to it i had the black screen and cant solved it

even cant return to fluxbox or xfce (i found x11 problem i think its tmp file problem iirc)

so i installed sway and its works

but when i put fastfetch i found the storage is full 100% and cant do anything when i reboot even if tried tty

so any advice or just format this partition and move to new distro (actually i had bad experinces, alas, but not forced to say this distro is bad)

 

[osprey]

i think the title is bad so i will edit it soon

so when i try to setup wayland in my second distro (20gb storage) first i tried labwc and when i entered to it i had the black screen and cant solved it

even cant return to fluxbox or xfce (i found x11 problem i think its tmp file problem iirc)

so i installed sway and its works

but when i put fastfetch i found the storage is full 100% and cant do anything when i reboot even if tried tty

so any advice or just format this partition and move to new distro (actually i had bad experinces, alas, but not forced to say this distro is bad)

If the installed operating system won't function because the drive is full, then in the first instance, one can create space by identifying the larger files and removing those that can be removed without disturbing the system. If it can't be done on the system itself because it won't run, then it can be done by using a live disk and mounting the relevant partitions to remove files to create space.

There may be files in the home directory or in the system files that can safely be removed. The user will need to identify files in their home directory. For system files, the ones that can usually be removed safely are journal files under the /var/log directory and files in the /var/cache directory. Note that removing the files should not also remove the directory structure though in the case if the system files.

If one needs to use a live disk to remove files, then they can boot the live disk, or a rescue disk, identify the partitions on the drive by running the command: lsblk, and then mounting the relevant partitions like / or
/home/$USER, and then hunt for large files to remove.

Another alternative is to back up the data you want to keep and re-install to create a newly partitioned system that will not consume all the disk space.

In the spoiler is an example of meticulous, laborious example of finding files to remove.

Spoiler: File removal example from live disk

If you wish to make a meticulous and detailed removal that takes some time but has the advantage of precision, the following is an example using a live disk:
Boot the live disk and run lsblk:

[~]$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sr0          11:0    1  1024M  0 rom
nvme0n1     259:0    0 465.8G  0 disk
├─nvme0n1p1 259:1    0   476M  0 part /boot/efi
├─nvme0n1p2 259:2    0  14.9G  0 part [SWAP]
└─nvme0n1p3 259:3    0 450.4G  0 part /
<snip>

There's only a root partition, so that can be mounted on the directory /mnt:

# mount /dev/nvme0n1p3 /mnt

To find out where the largest files are, one can run a command like the following. I'll leave the description of the options for the reader to unravel from the man pages:

# du -hx /mnt | sort -hr | head -n 10
35G /mnt/home/ben
9.1G    /mnt/home/ben/sundry/ufn
9.1G    /mnt/home/ben/sundry
6.1G    /mnt/home/ben/sundry/ufn/old
5.8G    /mnt/home/ben/browsers
4.4G    /mnt/home/ben/music
4.1G    /mnt/home/ben/music/tunes
3.7G    /mnt/home/ben/music/tunes/musicbooks
3.0G    /mnt/home/ben/Downloads
2.7G    /mnt/home/ben/lemon

The output shows a bunch of directories where the big files are. Looking into one of those directories for example:

# ls -al /mnt/home/ben/sundry/ufn
total 40
drwxrwxr-x 9 ben ben 4096 Mar 27 17:08 .
drwxr-xr-x 5 ben ben 4096 Apr 27 11:02 ..
drwxrwxr-x 2 ben ben 4096 Mar 27 17:06 ff
drwxrwxr-x 2 ben ben 4096 Mar 27 17:06 fm
drwxrwxr-x 2 ben ben 4096 Mar 27 17:06 mfj
drwxrwxr-x 2 ben ben 4096 Mar 27 17:07 moso
drwxrwxr-x 2 ben ben 4096 Mar 27 17:07 msg
drwxrwxr-x 2 ben ben 4096 Mar 27 17:08 mst
drwxrwxr-x 2 ben ben 4096 Mar 27 17:08 rn

Then finding the space they all take:

# du -sh /mnt/home/ben/sundry/ufn
6.1G    .

The output shows 6.1G. If all of that can be dispensed with, including all of those directories and files, run:

# rm -rf /mnt/home/ben/sundry/ufn/old/*

Otherwise you can look into one of those directories, find out how much space it takes up, and just remove what is there:

# ls -al /mnt/sundry/ufn/old/moso
total 1.5G
-rw-rw-r-- 1 ben ben  32M Mar 27 17:06 10-1.mp4
-rw-rw-r-- 1 ben ben  28M Mar 27 17:06 10-2.mp4
-rw-rw-r-- 1 ben ben  34M Mar 27 17:07 10-3.mp4
-rw-rw-r-- 1 ben ben  33M Mar 27 17:07 10.mp4
-rw-rw-r-- 1 ben ben  37M Mar 27 17:07 1130.mp4
-rw-rw-r-- 1 ben ben  37M Mar 27 17:07 11.mp4
-rw-rw-r-- 1 ben ben  45M Mar 27 17:07 16.mp4
-rw-rw-r-- 1 ben ben  67M Mar 27 17:07 18.mp4
-rw-rw-r-- 1 ben ben  68M Mar 27 17:06 21x4.mp4
-rw-rw-r-- 1 ben ben 9.0M Mar 27 17:07 2.mp4
-rw-rw-r-- 1 ben ben 111M Mar 27 17:07 35.mp4
-rw-rw-r-- 1 ben ben 130M Mar 27 17:07 36.mp4
-rw-rw-r-- 1 ben ben 127M Mar 27 17:07 40.mp4
-rw-rw-r-- 1 ben ben 202M Mar 27 17:07 54.mp4
-rw-rw-r-- 1 ben ben 206M Mar 27 17:06 58.mp4
-rw-rw-r-- 1 ben ben 224M Mar 27 17:07 62.mp4
-rw-rw-r-- 1 ben ben  26M Mar 27 17:06 8.mp4
-rw-rw-r-- 1 ben ben  31M Mar 27 17:07 9-43.mp4

The ls command above shows the space taken up as 1.5G. One can also run the du command to see:

# du -sh /mnt/home/ben/sundry/ufn/old/moso
1.5G    .

If the files are expendable, they can be removed with:

# rm /mnt/sundry/ufn/old/moso/*

When the work is finished, one unmounts the /mnt directory:

# umount /mnt

Then poweroff and withdraw the live disk, and boot the system to see if it runs. Linux systems run well when under about 85% full. They can get sluggish in the mid 90s and fail in the late 90s.

 

[lazy_lain]

lol when i read mount command i remember the live iso (and not to do it in tty)

after puting sudo du -hx /mnt | sort -hr | head -n 10

23G    /mnt
13G    /mnt/var
9.5G    /mnt/var/log
7.0G    /mnt/usr
3.9G    /mnt/usr/lib
2.6G    /mnt/var/lib
2.4G    /mnt/usr/share
2.3G    /mnt/var/lib/flatpak
2.2G    /mnt/var/lib/flatpak/repo/objects
2.2G    /mnt/var/lib/flatpak/repo

so checked the var/log with ls -al /mnt/var/log

-rw-r-----   1 root       adm   9934147778 May  5 15:35 auth.log

so sudo rm /mnt/var/log/auth.log

and then sudo du -hx /mnt | sort -hr | head -n 10

14G    /mnt
7.0G    /mnt/usr
3.9G    /mnt/usr/lib
3.0G    /mnt/var
2.6G    /mnt/var/lib
2.4G    /mnt/usr/share
2.3G    /mnt/var/lib/flatpak
2.2G    /mnt/var/lib/flatpak/repo/objects
2.2G    /mnt/var/lib/flatpak/repo
2.1G    /mnt/swap

but alas i dont read the auth log to know where is the exact problem

but i will fix the waylad problem
thx <3