MX Linux Forum

Posted: **Fri Jan 03, 2025 10:05 am**

I recently did a clean install of MX-23-kde, 64-bit, which to all indications went very smoothly. The only changes I made relative to the previous distro (19.4) I was to expand the size of the root (20GB to 30GB) and the home partition from 50 to 65GB. After installation I updated all of the installed packages (I was a bit surprised at the number, it was hundreds) and brought in some stuff I use, eg, openshot, and set about to fix things up to my personal liking, eg, themes etc. I keep my personal data on a separate partition. I'd post a screen shot of the drive but apparently do not have ksnip installed and apt can't install anything, no room in /var, so that will have to wait until I free up some space. I looked on line for some help and found one similar description of a problem but the solutions (ncdu) don't work for me now because I can't install that application either. This install is only about a week old so I was pretty surprised to see the partition full. I've used MX from back in the mepis days and have it on about 4 computers but have never seen this. Any thoughts?

I noticed that the info in my profile is woefully out of date. This machine is a lenovo ideapad 330. The HD is 256GB and it has 8GB ram

Posted: **Fri Jan 03, 2025 10:09 am**

You need to post the output from the QSI utility. The Quick System Info (QSI) utility is located in MX Tools and its output is automatically formatted for use here in the forum. Run the QSI utility, click “Copy for Forum” at the bottom and then just paste it here in your thread.
Forum Rules

Posted: **Fri Jan 03, 2025 10:21 am**

whbr wrote: Fri Jan 03, 2025 10:05 am After installation I updated all of the installed packages (I was a bit surprised at the number, it was hundreds)

While we're waiting on the QSI, it may be useful in the future to know that the MX team maintains patched snapshots of the Xfce and KDE release ISOs. These snapshots are usually uploaded once a month, unless they're busy working on an upcoming new release or have just recently published one.

Posted: **Fri Jan 03, 2025 10:49 am**

MX Cleanup also provides easy ways to remove excess cached files, as well as graphical tools that allow you to see which folders/files are taking up the most space.

After all those updates, cached deb files are no doubt taking up some of that limited space in root, and odds are you'll never use them.

You could also remove any extra kernels in MX Cleanup if you're happy with the latest one.

Posted: **Fri Jan 03, 2025 11:04 am**

Code: Select all

System:
  Kernel: 6.1.0-28-amd64 [6.1.119-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-28-amd64 root=UUID=<filter> ro quiet splash
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.4_KDE_x64 Libretto
    September 15 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: Dell product: Inspiron 5567 v: N/A serial: <superuser required> Chassis:
    type: 10 serial: <superuser required>
  Mobo: Dell model: 01W6F7 v: A00 serial: <superuser required> UEFI: Dell v: 1.2.8
    date: 05/22/2019
Battery:
  ID-1: BAT0 charge: 36.2 Wh (100.0%) condition: 36.2/42.0 Wh (86.1%) volts: 12.7 min: 11.4
    model: Samsung SDI DELL CYMGM77 type: Li-ion serial: <filter> status: full
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
    charge: 55% (should be ignored) rechargeable: yes status: discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard K540/K545 serial: <filter>
    charge: 50% (should be ignored) rechargeable: yes status: N/A
CPU:
  Info: model: Intel Core i5-7200U bits: 64 type: MT MCP arch: Amber/Kaby Lake note: check
    gen: core 7 level: v3 note: check built: 2017 process: Intel 14nm family: 6 model-id: 0x8E (142)
    stepping: 9 microcode: 0xF6
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache: L1: 128 KiB
    desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 683 high: 701 min/max: 400/3100 scaling: driver: intel_pstate
    governor: powersave cores: 1: 700 2: 701 3: 700 4: 632 bogomips: 21599
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel arch: Gen-9.5
    process: Intel 14nm built: 2016-20 ports: active: HDMI-A-1 off: eDP-1 empty: none bus-ID: 00:02.0
    chip-ID: 8086:5916 class-ID: 0300
  Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-5:5
    chip-ID: 0c45:6a06 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 506x285mm (19.92x11.22") s-diag: 581mm (22.86")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: primary model: Samsung C27F398 serial: <filter>
    built: 2017 res: 1920x1080 hz: 60 dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23")
    diag: 686mm (27") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  Monitor-2: eDP-1 note: disabled model: BOE Display 0x0671 built: 2016 res: 1920x1080 dpi: 101
    gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: 1366x768
  API: OpenGL v: 4.6 Mesa 24.2.2-1~mx23ahs renderer: Mesa Intel HD Graphics 620 (KBL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel v: kernel
    alternate: snd_soc_skl,snd_sof_pci_intel_skl bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403
  API: ALSA v: k6.1.0-28-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Wireless 3165 driver: iwlwifi v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:3165 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8136 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-8:7
    chip-ID: 8087:0a2a class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 57 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
    sub-v: 1000 hci-v: 4.2 rev: 1000
  Info: acl-mtu: 1021:5 sco-mtu: 96:6 link-policy: rswitch hold sniff
    link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
    telephony
Drives:
  Local Storage: total: 3.87 TiB used: 92.03 GiB (2.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: SK Hynix model: SC311 SATA 256GB size: 238.47 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 0P10
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Western Digital model: WD40EZRZ-00GXCB0
    size: 3.64 TiB block-size: physical: 4096 B logical: 512 B type: HDD rpm: 5400 serial: <filter>
    rev: 4004 scheme: GPT
Partition:
  ID-1: / raw-size: 29.41 GiB size: 28.78 GiB (97.86%) used: 28.77 GiB (99.9%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 500 MiB size: 496 MiB (99.20%) used: 62.5 MiB (12.6%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 65.43 GiB size: 63.85 GiB (97.59%) used: 10.05 GiB (15.7%) fs: ext4
    dev: /dev/sda7 maj-min: 8:7
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 3 GiB used: 169.4 MiB (5.5%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 38.0 C pch: 34.0 C mobo: 30.0 C sodimm: SODIMM C
  Fan Speeds (RPM): cpu: 0
Repos:
  Packages: pm: dpkg pkgs: 2582 libs: 1354 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
    2: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm ahs
Info:
  Processes: 216 Uptime: 19h 27m wakeups: 35 Memory: 7.66 GiB used: 2.89 GiB (37.7%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Posted: **Fri Jan 03, 2025 11:19 am**

@whbr
The qsI that you have posted is from a Dell Inspiron but not from the problem Lenovo Ideapad, which is the one we need to see.

Posted: **Fri Jan 03, 2025 11:34 am**

As j2mcgreg mentioned this looks from a different device, but maybe not since I see root is full.

First thing you might want to do is to run a "sudo apt clean" to get rid of the apt cache, then you probably need to examine what is the largest stuff in your root, 28GB is a lot of stuff, use Filelight (or ncdu in command line) to see what folders/files take most of the space, don't rush to delete anything, see first if something looks out of ordinary.

Posted: **Fri Jan 03, 2025 11:50 am**

Thank you for directing me to the MX Cleanup. If I interpreted this correctly the disk analysis tool showed that /var/log is taking up 16GB of the root partition. That is about equally spread between /var/log/syslog and /var/log/kern.log The default option for deleting logs is not accessed for 7 days. When I ran it very little was removed so I guess this has blown up more recently than that. Is there any danger in setting that to 0 days? What would you recommend? Any suggestions on the other settings would be appreciated as well.

Sorry about the confusion on the machine. I have two laptops on my desk that I am installing MX-23 on and the one on top was the lenovo. I was looking at the Dell on an external monitor. The Dell is the machine I'm having issues with and the one as you noted that I post the qsl from. While I was at it I ran the disk analysis tool in MX cleanup on the lenovo and suffice it to say the output bears no resemblance to that I see with the Dell

Posted: **Fri Jan 03, 2025 12:17 pm**

Yeah, it appears something is spamming those logs. Try setting it to one day first before deleting, just to see how big they get then, but you can remove the current ones with

Code: Select all

sudo rm /var/log/syslog /var/log/kern.log

The Quick System Info also lets you see what's in those and many other logs, but don't let them get huge before trying to view them. I see Variety is spamming mine with not be able to find any local "funny" quotes...hey, comedy is hard!

Code: Select all

2024-12-29T00:03:44.665739-08:00 dellmx23 bash[2901]: WARNING: 2024-12-29 00:03:44,665: get_one_quote() 'No quotes for 'funny' for plugin Local text files'

I also see in my own var/log folder there are numerous gzipped archived copies of older logs that can be removed, I would suggest those also get cleaned out...can you check those in Dolphin?

Posted: **Fri Jan 03, 2025 12:47 pm**

So with Dolphin I see both syslog and kern.log as being 7.8GB which is what the disk analyser reported. I poked around a little but didn't see anything that caught my attention.. Can these two files be deleted. They seem to be just straight up files so it would seem to me to be all or nothing. I ran apt clean as Adrian suggested but that didn't free much as I guess that is not where the problem was.

Posted: **Fri Jan 03, 2025 12:57 pm**

Yes, go ahead and get rid of them.

But they'll come back and start growing like crazy again, so a separate thread will be about what's making them so big (spamming them).

Posted: **Fri Jan 03, 2025 1:16 pm**

I took from your previous post that I could remove them so ran the rm command from the terminal and it certainly had the desired effect of freeing up a lot of space on root. I am curious as to how this came to pass, if there is anything else I should be looking out for. I leave this out there for a while to see if anyone else have any thoughts they'd like to share. But so far, thanks a million for your prompt assistance and kind suggestions.

Posted: **Fri Jan 03, 2025 1:17 pm**

I missed your reply Stevo. I'll keep and eye on this for a while and see about a new thread.

Posted: **Fri Jan 03, 2025 2:12 pm**

@whbr wrote:

I am curious as to how this came to pass, if there is anything else I should be looking out for

You may never find what's causing the logging function to run amok, but on your next install you can restrict the logs' size by creating a separate partition: /var/log and setting its size to about two GiB.

Posted: **Fri Jan 03, 2025 4:03 pm**

Here are two MX Linux threads that are related to the issue of the /var/log/syslog and /var/log/kern.log getting excessively large. The first Bullet-Point link has a two solutions (Post #43 is one and Post #30 is the other, which just gives a link to another forum and solution). The second Bullet-Point link is not really a "fix" but more accurately a work-around or "Band-Aid fix" because it does not identify the root cause of the problem. It shows how to limit the size of the log files.

viewtopic.php?p=676749#p676749 "Var log disk space issue" is a March 2022 Post #43 that contains the solution (the problem was the USB wi-fi adapter was turned off and a PCI wi-fi adapter was turned on).

Post #25 said the errors stopped after changing the wi-fi module.

Post #30 linked to a thread on the proxmox.com forum that had the same problem and solved by replacing a NIC (Network Interface Card) as shown here https://forum.proxmox.com/threads/solve ... ost-228396.

viewtopic.php?p=759430#p759430 "System continues to grow up, MX-23" is a January 2024 Post #9 that shows how to limit the maximum size of the log, further amplified in "Charlie Brown's" Post #18 that said:
(... So, what we do is: Limit the size, and say when it exceeds 1M it'll create a second (new) file to go on... however the number of files are also limited (to 4 by default, which we can change), that means: it'll be cleaning all the time "by itself" as a result (removing the oldest file and creating anew)
Post #20 gives additional information on how to limit the size.

Posted: **Mon Jan 06, 2025 10:08 am**

I've been watching the /var/log files and as suggested by Stevo they are slowly ballooning. I think if one of the admins wanted to mark this solved that would be good. I know what the problem is and that was the purpose of the original post. I'll putter with this as I have time and if I come up with anything useful will start a new thread, as recommended. Thanks for all your attention to my problem.

Posted: **Mon Jan 06, 2025 11:00 am**

@whbr
You as the original poster mark the post that solves your issue by clicking on the check mark at the top of that post.

Posted: **Mon Jan 06, 2025 1:16 pm**

whbr wrote: Mon Jan 06, 2025 10:08 am I know what the problem is and that was the purpose of the original post.

Mind you telling us, what the issue was and what you changed to fix it. Potential some kernel-bootparameter to avoid spamming the log-files.
OTOH, ok ignoring the original issue and just keep the logfiles small by removing, e.g with logrotate is a reasonable workaround option, but not what I would call fix.

MX Linux Forum

root partition full

root partition full

Re: root partition full

Re: root partition full

Re: root partition full

Re: root partition full

Re: root partition full

Re: root partition full

Re: root partition full

Re: root partition full

Re: root partition full

Re: root partition full [Solved]

Re: root partition full

Re: root partition full

Re: root partition full

Re: root partition full

Re: root partition full

Re: root partition full

Re: root partition full