After update today (01 March 22) BTFRS and baloo_file_extractor again running amok

Issues & Assistance
1

My inxi copy/pasted from last week:

System:
  Kernel: 5.16.7-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=6cafe1ae-53e0-4003-8e56-0566259c4051
    rw [email protected] loglevel=3 quiet
  Desktop: KDE Plasma 5.24.0 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM
    Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: All Series v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: H97M-E v: Rev X.0x serial: <superuser required> UEFI: American Megatrends
    v: 2702 date: 03/28/2016
CPU:
  Info: model: Intel Core i5-4690 bits: 64 type: MCP arch: Haswell family: 6 model-id: 0x3C (60)
    stepping: 3 microcode: 0x28
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB
    L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 3468 high: 3493 min/max: 800/3900 scaling: driver: intel_cpufreq
    governor: performance cores: 1: 3493 2: 3492 3: 3493 4: 3396 bogomips: 27937
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  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: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: ASUSTeK
    driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:0412 class-ID: 0300
  Device-2: Logitech HD Webcam C615 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 3-3:2
    chip-ID: 046d:082c class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver: loaded: intel
    unloaded: modesetting alternate: fbdev,vesa display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 422x237mm (16.6x9.3") s-diag: 484mm (19.1")
  Monitor-1: HDMI2 res: 1600x900 hz: 60 dpi: 58 size: 700x390mm (27.6x15.4") diag: 801mm (31.5")
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 21.3.5 compat-v: 3.0
    direct render: Yes
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c class-ID: 0403
  Device-2: Intel 9 Series Family HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
    bus-ID: 00:1b.0 chip-ID: 8086:8ca0 class-ID: 0403
  Device-3: Logitech HD Webcam C615 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 3-3:2
    chip-ID: 046d:082c class-ID: 0e02 serial: <filter>
  Sound Server-1: ALSA v: k5.16.7-zen1-1-zen running: yes
  Sound Server-2: JACK v: 1.9.20 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.45 running: no
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK AM1I-A
    driver: r8169 v: kernel port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
  Device-2: Ralink RT5572 Wireless Adapter type: USB driver: rt2800usb bus-ID: 3-10:5
    chip-ID: 148f:5572 class-ID: 0000 serial: <filter>
  IF: wlp0s20u10 state: up mac: <filter>
Drives:
  Local Storage: total: 4.55 TiB used: 1.82 TiB (40.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD5000AACS-00ZUB0 size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1B01
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD40EFRX-68WT0N0 size: 3.64 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 0A82 scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WD5000LPVX-80V0TT0
    size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400
    serial: <filter> rev: 1A01 scheme: GPT
Partition:
  ID-1: / raw-size: 465.5 GiB size: 4.09 TiB (900.43%) used: 1.82 TiB (44.4%) fs: btrfs
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%) used: 546 KiB (0.2%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 465.5 GiB size: 4.09 TiB (900.43%) used: 1.82 TiB (44.4%) fs: btrfs
    dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 465.5 GiB size: 4.09 TiB (900.43%) used: 1.82 TiB (44.4%) fs: btrfs
    dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 465.5 GiB size: 4.09 TiB (900.43%) used: 1.82 TiB (44.4%) fs: btrfs
    dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.32 GiB used: 2 MiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C
  Fan Speeds (RPM): N/A

I have been doing daily updates by garuda-update and everything has been running smoothly. After doing my update today things seemed okay until I tried to start a Debian vm in virtualbox. It would not start, then locked up the computer. Upon restart my hdd was making a lot of noise and running constantly, just like it was doing last week when we had this same conversation (see [SOLVED] Btfrs and baloo_file_extractor issue). I have now disabled ALL btfrs utilities in the BTFRS Assistant and disabled baloo by balooctl disable.

I am now typing on my macbook, because my linux box is virtually unusable, due to pauses and locking up.

So...what just happened?

2

What did you update or change just before the problem started?

Also just to note, this:

seems to be older than your inxi from 18 days ago:

1 Like
3

My how time flies.

The computer is again working (I'm typing on it now), after I disabled the BTRFS utilities and baloo, but pretty slow. I have been putting my computer to sleep, rather than shutting down lately. This afternoon I woke it up, logged on, then did garuda-update. I did a couple google searches and downloaded a couple files, then tried to open my Debian vm in virtualbox. The Debian 10 boot-up was full of errors an did not complete. I then opened the Devices window in virtualbox and selected the mouse option and my mouse immediately disappeared and the computer stopped responding to anything. I performed a hard reset on the computer. Upon reboot the bootup process was laggy and the hard drive immediately became very active. The bootup took around 20 minutes and once the desktop came up it was unusable, due to pauses and lockups. I finally got enough response to get BTRFS Assistant to come up, at which time I deselected ALL BTRFS services and timers. I also was able to get a terminal up and disabled baloo. A reboot was a little faster, but not much. However, I am now able to at least use the computer. Still pretty slow, but working. Even with baloo disabled, I can still hear my hdd working incessantly.

I deleted the Debian vm and am reinstalling it. Seems to be working. I noticed the VirtualBox Manager page looks different, so I expect there was an update there.

Here's my current inxi: 
System:
  Kernel: 5.16.11-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=6cafe1ae-53e0-4003-8e56-0566259c4051 rw [email protected]
    loglevel=3 quiet
  Desktop: KDE Plasma 5.24.2 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
    vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: All Series v: N/A
    serial: <superuser required>
  Mobo: ASUSTeK model: H97M-E v: Rev X.0x serial: <superuser required>
    UEFI: American Megatrends v: 2702 date: 03/28/2016
CPU:
  Info: model: Intel Core i5-4690 bits: 64 type: MCP arch: Haswell family: 6
    model-id: 0x3C (60) stepping: 3 microcode: 0x28
  Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB
    desc: 1x6 MiB
  Speed (MHz): avg: 3522 high: 3632 min/max: 800/3900 scaling:
    driver: intel_cpufreq governor: performance cores: 1: 3473 2: 3492 3: 3632
    4: 3492 bogomips: 27934
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf
    mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  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: Full generic retpoline, IBPB: conditional,
    IBRS_FW, STIBP: disabled, RSB filling
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
    vendor: ASUSTeK driver: i915 v: kernel ports: active: HDMI-A-2
    empty: HDMI-A-1,VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0412 class-ID: 0300
  Device-2: Realtek RTL2838 DVB-T type: USB driver: N/A bus-ID: 3-2.1:4
    chip-ID: 0bda:2838 class-ID: 0000 serial: <filter>
  Device-3: Logitech HD Webcam C615 type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 3-3:3 chip-ID: 046d:082c
    class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.3 compositor: kwin_x11 driver: X:
    loaded: intel unloaded: modesetting alternate: fbdev,vesa gpu: i915
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 422x237mm (16.6x9.3")
    s-diag: 484mm (19.1")
  Monitor-1: HDMI2 mapped: HDMI-A-2 model: LCD-TV serial: <filter>
    built: 2007 res: 1600x900 hz: 60 dpi: 58 gamma: 1.2
    size: 700x390mm (27.6x15.4") diag: 801mm (31.5") ratio: 16:9 modes:
    max: 1280x720 min: 720x400
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2)
    v: 4.5 Mesa 21.3.7 compat-v: 3.0 direct render: Yes
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 00:03.0
    chip-ID: 8086:0c0c class-ID: 0403
  Device-2: Intel 9 Series Family HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0
    class-ID: 0403
  Device-3: Logitech HD Webcam C615 type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 3-3:3 chip-ID: 046d:082c
    class-ID: 0e02 serial: <filter>
  Sound Server-1: ALSA v: k5.16.11-zen1-1-zen running: yes
  Sound Server-2: JACK v: 1.9.20 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.47 running: no
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK AM1I-A driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
  Device-2: Ralink RT5572 Wireless Adapter type: USB driver: rt2800usb
    bus-ID: 3-10:7 chip-ID: 148f:5572 class-ID: 0000 serial: <filter>
  IF: wlp0s20u10 state: up mac: <filter>
Drives:
  Local Storage: total: 4.55 TiB used: 1.36 TiB (29.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD5000AACS-00ZUB0 size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 1B01
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD40EFRX-68WT0N0 size: 3.64 TiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 0A82 scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Western Digital
    model: WD5000LPVX-80V0TT0 size: 465.76 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 1A01 scheme: GPT
Partition:
  ID-1: / raw-size: 465.5 GiB size: 4.09 TiB (900.43%) used: 1.36 TiB (33.2%)
    fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.45%)
    used: 546 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 465.5 GiB size: 4.09 TiB (900.43%)
    used: 1.36 TiB (33.2%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 465.5 GiB size: 4.09 TiB (900.43%)
    used: 1.36 TiB (33.2%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 465.5 GiB size: 4.09 TiB (900.43%)
    used: 1.36 TiB (33.2%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.32 GiB used: 101 MiB (0.6%)
    priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 223 Uptime: 43m wakeups: 0 Memory: 15.32 GiB
  used: 3.36 GiB (21.9%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.2.0 clang: 13.0.1 Packages: pacman: 1759 lib: 409 Shell: fish
  v: 3.3.1 default: Bash v: 5.1.16 running-in: alacritty inxi: 3.3.13
Garuda (2.5.5-1):
  System install date:     2021-03-08
  Last full system update: 2022-03-01
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       No/Undetected
  Snapshots:               Timeshift
  Failed units:            nmb.service
4

If you update the kernel then you really should reboot. Connecting devices or running software with kernel modules (like Virtualbox) won't work as expected until then.

This is basically the premier way of damaging a filesystem; while journaling can help, hard resets are never safe.

Have you considered that the disk itself might be failing?

Check the output of dmesg or journalctl and check for any SMART status with smartctl.

It's also worth performing a RAM test as failing RAM can also produce filesystem corruption that will create seemingly "random" issues.

4 Likes
5

IMO you have several issues going on here. Instead of disabling the Garuda BTRFS utilities, you should have diabled btrfs quotas. Qgroup usage can lead to major system slowdowns and at times lock up your computer entirely.

Disable BTRFS Quota (qgroups)

Garuda and other distributions have numerous reports linking system freezes with btrfs quota's being enabled. Disabling btrfs quotas would be a logical step if you experience freezes during balancing operations. if you do experience a freeze during a balancing operation, try waiting as long as possible to let things hopefully resolve on their own.

Read the link below for information on how to disable qgroups:

BTRFS quota is automatically re-enabled if I disable it

To disable BTRFS quota's run:

sudo btrfs quota disable /

Disabling qgroups will impact timeshift's ability to gauge the remaining space left for creating snapshots. However, with qgroups enabled on your computer it might feel sluggish, or even grind completely to a halt. It has also been reported that the more snapshots you have, the worse this issue can become.

Documentation regarding quota support in BTRFS:

BTRFS Quota support

There has been some discussion about making qgroups disabled by default with Garuda. At the time of writing this, I believe BTRFS quotas are still enabled by default in all editions.

Unfortunately it seems some updates may re-enable qroups, so you need to check regularly to be sure they stay disabled.

Disable Baloo

The exact same re-enablement can happen with Baloo. If you don't take extra precautions KDE updates have a bad habit of re-enabling Baloo as well.

Disable baloo in System Settings -> Search -> Uncheck Enable File Search

Then issue these commands:

balooctl stop
balooctl suspend
balooctl disable

edit the following file:

~/.config/baloofilerc

Add these lines:

[Basic Settings]
Indexing-Enabled=false

Remove all unneeded baloo index files if they weren't deleted automatically when baloo was disabled.

They are stored at:

 ~/.local/share/baloo/

Here are the steps listed in the Archwiki to make sure baloo remains disabled.

See:

https://wiki.archlinux.org/title/Baloo#Disabling_the_indexer

A pacman hook I wrote a while back to make doubly sure baloo doesn't get resurrected from the grave:

Creating useful pacman-hooks (by @tbg)

8 Likes
6

So what is this all about? Did a SAMBA server fail?

7

Thanks for all the replies and info. Thanks for the links about the quotas and qgroups issues. That was good information. Up until I read those I had no idea what "quotas" was. I hope the Garuda group decides to disable those options by default until they are refined a little more and become less problematic.

I have disabled qgroups in /etc/timeshift/timeshift.json and I disabled baloo and installed the hook prescribed above. We'll see how that works.

As for the nmb.service failure, not sure what happened. It just popped up several seconds after the inxi results printed. Not something I'm particularly concerned about just at this moment. I'll look at that once I get my computer back to usability!

I get no warnings in smartctl on the hard drives and the ram is fairly new...although it is a used motherboard and cpu. I am pretty convinced that quotas and baloo are my problems. Again, we'll see how the above changes affect things.

Thanks again.

1 Like
8

No change. HDD still very active. I am seeing with HTOP that baloo_file_extractor is still running, despite the hook and reboot. It is still running even after I have disabled baloo with:

sudo balooctl disable now

However, when I ran:

sudo killall Baloo_file_extractor

my hdd silenced immediately. Looking at /usr/bin, there is a file 'baloo_file' and a file 'baloo_file_extractor'. Should they both be part of the hook script or is 'baloo_file' sufficient?

9

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.