https://bugs.kde.org/show_bug.cgi?id=333433

Torsten Eichstädt <t.eichsta...@gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|Linux                       |FreeBSD
                 CC|                            |t.eichsta...@gmx.net
         Resolution|FIXED                       |---
     Ever confirmed|0                           |1
           Platform|Kubuntu Packages            |FreeBSD Ports
             Status|RESOLVED                    |REOPENED

--- Comment #4 from Torsten Eichstädt <t.eichsta...@gmx.net> ---
kf5-baloo-5.68.0, FreeBSD 12.1-RELEASE-p6, installed from package (not
self-compiled)
Hi,

I ran into this when I null-mounted (unionfs) three big source trees into my
$HOME.  Although otherwise the handling of these mounts is absolutely stable, I
think it's a bug in FreeBSD: how can an indexer running at lowest priority
(nice 19 and ordinary non-root UID) freeze the whole system?  But maybe it's
rooted in some Qt lib, KDE frameworks or baloo, or that one of these uses the
VFS in an incorrect manner.

Symptoms: 
1. When an index already exists and baloo is enabled, the whole system becomes
so unresponsive that it's impossible to do anything.  I had to force a shutdown
by pressing the power button >4 seconds, reboot, and manually disable baloo in
~/.config/baloofilerc.
2. When no index exists and baloo gets enabled, the system becomes very
sluggish, like described in the initial bug report, some windows do not refresh
correctly, besides that the system & GUI is more or less usable.
3. Stopping a running baloo indexer with 'balooctl purge' fails, neither does
'balooctl disable' help.  It has to be killed manually.

Workaround (does not hurt in my case since source code is not indexed anyway):
1. kill baloo and delete an existing index: 'balooctl purge'
2. Add the union-mount directories to excluded dirs in systemconfig
   -> ~/.config/baloofilerc:exclude folders[$e]=$HOME/Projects/FreeBSD/src
3. Enable baloo in systemconfig

I do reopen this bug, and it would be great if someone with deeper knowledge of
VFS handling adds some comment on this.
My /etc/fstab:
/src/13-CUR     /home/paul/Projects/FreeBSD/src/13-CUR unionfs 
rw,late,below,noatime 0 0
/src/12-STABLE  /home/paul/Projects/FreeBSD/src/12-STABLE unionfs
rw,late,below,noatime 0 0
/src/12.1-REL   /home/paul/Projects/FreeBSD/src/12.1-REL unionfs
rw,late,below,noatime 0 0

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to