Juan Erbes <jerbes@gmail.com> writes:
El dom., 17 feb. 2019 a las 18:49, <ub22@gmx.net> escribió:
Hi,
Gesendet: Freitag, 15. Februar 2019 um 10:33 Uhr; Von: "Axel Braun"
I can't find the reason but my PCs are unusable since them (randomly between 1 and 10 minutes the system hangs and sometimes it will be operabel after 5 to 10 minutes - sometimes only a reset of the desktop via <strg>+<alt>+<back> key helps. No one of my family are able to work anymore especially in case of the fact that Editing of a file will sometimes broken!
Check your background jobs for heavy disk activities - or in your case, network activities (home was on a NFS share, right?). Baloo indexer might be a candidate, btrfs maintenance as well.
Yes - /home was mounted on the Server xxx (192.168.111.1)
Client: cat /etc/fstab 192.168.111.1:/home /home nfs4 defaults 0 0 [...]
Server: cat /etc/fstab UUID=xyz /home ext4 defaults 0 0 /home /mnt/nfs4/home none bind 0 0 [...]
I remember a KDE update some time ago that changed the structure of the database (if I'm not mistaken), that caused my destop to be unuseable as well for some time. After the dust has settled, all back to normal
Now I checked the server with a second PC and during the time the test systems hang (mainly in KDE plasma - and now I can see on the CPU monitor, that at min. one CPU is running on 100% during the time the system hangs).
At the second PC I can find in the log Feb 17 22:11:00 xxx kernel: nfs: server 192.168.111.1 not responding, still trying
# zypper se Baloo [...] S | Name | Zusammenfassung | Typ --+--------------------------+-----------------------------------------------+------ | baloo5-devel | Development package for baloo5 | Paket i | baloo5-file | Filesearch components for Baloo Framework | Paket i | baloo5-file-lang | Translations for package baloo5 | Paket i | baloo5-imports | QML components for Baloo Framework | Paket i | baloo5-imports-lang | Translations for package baloo5 | Paket i | baloo5-kioslaves | KIO slave components for Baloo Framework | Paket i | baloo5-kioslaves-lang | Translations for package baloo5 | Paket i | baloo5-tools | Aditional components for Baloo Framework | Paket i | baloo5-tools-lang | Translations for package baloo5 | Paket i | baloo5-widgets | Framework for searching and managing metadata | Paket | baloo5-widgets-devel | Development package for baloo5-widgets | Paket i | baloo5-widgets-lang | Translations for package baloo5-widgets | Paket i | libKF5Baloo5 | Core library for Baloo Framework | Paket | libKF5Baloo5-32bit | Core library for Baloo Framework | Paket i | libKF5BalooEngine5 | Baloo Engine library | Paket | libKF5BalooEngine5-32bit | Baloo Engine library | Paket i | libKF5BalooEngine5-lang | Translations for package baloo5 | Paket
# ps ax | grep -i baloo 28322 pts/6 S+ 0:00 grep --color=auto -i baloo
But systemload seams to be normal during the hanging time (also no entry beside named during this time in the journalctl log):
# head top-bn1_2019-02-17_* ==> top-bn1_2019-02-17_12:54:08.txt <== top - 12:54:08 up 11:22, 2 users, load average: 2.12, 5.34, 5.89 Tasks: 200 total, 1 running, 199 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 3.0 sy, 0.0 ni, 97.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15785.12+total, 1338.551 free, 1174.246 used, 13272.32+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14278.46+avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 162700 10412 7200 S 0.000 0.064 0:06.12 systemd 2 root 20 0 0 0 0 S 0.000 0.000 0:00.05 kthreadd 3 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 rcu_gp
==> top-bn1_2019-02-17_12:55:22.txt <== top - 12:55:22 up 11:24, 2 users, load average: 4.19, 5.18, 5.78 Tasks: 200 total, 1 running, 199 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 2.9 sy, 1.5 ni, 48.5 id, 47.1 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15785.12+total, 1332.992 free, 1174.430 used, 13277.70+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14278.27+avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 3525 root 39 19 670772 653112 5532 D 6.250 4.041 5:10.51 storeBackup 10961 root 20 0 8128 4124 3476 R 6.250 0.026 0:00.02 top 1 root 20 0 162700 10412 7200 S 0.000 0.064 0:06.12 systemd
==> top-bn1_2019-02-17_12:56:43.txt <== top - 12:56:43 up 11:25, 2 users, load average: 3.11, 4.72, 5.58 Tasks: 200 total, 1 running, 199 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 4.4 sy, 0.0 ni, 76.5 id, 19.1 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15785.12+total, 1326.566 free, 1174.949 used, 13283.60+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14277.76+avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1932 root 20 0 0 0 0 S 6.250 0.000 0:06.02 nfsd 1933 root 20 0 0 0 0 S 6.250 0.000 0:08.92 nfsd 1934 root 20 0 0 0 0 D 6.250 0.000 0:12.13 nfsd
==> top-bn1_2019-02-17_13:04:32.txt <== top - 13:04:33 up 11:33, 2 users, load average: 4.25, 3.59, 4.60 Tasks: 199 total, 1 running, 198 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.5 us, 1.5 sy, 0.0 ni, 70.6 id, 25.0 wa, 0.0 hi, 1.5 si, 0.0 st MiB Mem : 15785.12+total, 1214.164 free, 1177.508 used, 13393.45+buff/cache MiB Swap: 60.996 total, 60.996 free, 0.000 used. 14275.20+avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 162700 10412 7200 S 0.000 0.064 0:06.13 systemd 2 root 20 0 0 0 0 S 0.000 0.000 0:00.05 kthreadd 3 root 0 -20 0 0 0 I 0.000 0.000 0:00.00 rcu_gp
Remark - during the 15 min. the test systems hangs - seems to be no special load or something others which pop's in my eyes.
Hi!
You has verified the free disk space with command "df"? It looks like so: df
Not directly related, but: Please use `btrfs filesystem df` instead of df if you have a btrfs partition and want to measure free space. You'll get different results, which could matter if your filesystem is nearly full.
S.ficheros bloques de 1K Usados Disponibles Uso% Montado en devtmpfs 8157692 0 8157692 0% /dev tmpfs 8202896 63092 8139804 1% /dev/shm tmpfs 8202896 9816 8193080 1% /run tmpfs 8202896 0 8202896 0% /sys/fs/cgroup /dev/sdb1 41945088 35785932 5268900 88% / /dev/sdb1 41945088 35785932 5268900 88% /boot/grub2/x86_64-efi /dev/sdb1 41945088 35785932 5268900 88% /tmp /dev/sdb1 41945088 35785932 5268900 88% /boot/grub2/i386-pc /dev/sdb1 41945088 35785932 5268900 88% /srv /dev/sdb1 41945088 35785932 5268900 88% /var /dev/sdb1 41945088 35785932 5268900 88% /usr/local /dev/sdb1 41945088 35785932 5268900 88% /opt /dev/sdb1 41945088 35785932 5268900 88% /root /dev/sdb2 1910635004 1284943776 625691228 68% /home tmpfs 1640576 8 1640568 1% /run/user/1000
A pair weeks ago I must to delette the older btrfs snapshots, because /dev/sdb1 was near the 100%
Good luck! Juan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- Dan Čermák <dcermak@suse.com> Software Engineer Development tools SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org