[oS-en] iotop complains of missing feature in kernel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 cer@Telcontar:~> sudo /usr/sbin/iotop -o -d 3.3333 Total DISK READ : 1169.77 K/s | Total DISK WRITE : 12.79 K/s Actual DISK READ: 1168.61 K/s | Actual DISK WRITE: 48.84 K/s TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND 2041 be/4 news 490.70 K/s 0.00 B/s ?unavailable? texpire 9622 be/4 cer 0.00 B/s 6.98 K/s ?unavailable? firefox --sm-client-id 27~-9abbeba61260 [LS Thread] 8039 idle cer 679.07 K/s 0.00 B/s ?unavailable? tracker-miner-fs-3 12912 be/4 cer 0.00 B/s 5.81 K/s ?unavailable? firefox --sm-client-id 27~beba61260 [IndexedDB #45] * * ... CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO % cer@Telcontar:~> uname -a Linux Telcontar 5.14.21-150400.24.33-default #1 SMP PREEMPT_DYNAMIC Fri Nov 4 13:55:06 UTC 2022 (76cfe60) x86_64 x86_64 x86_64 GNU/Linux cer@Telcontar:~> - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCY850Sxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVjxsAnREQY/RUTyYZuN8ZczMy KHE36e4GAJ9E6Pia/flb5Of5gQuYU1S9i0oirA== =W0vq -----END PGP SIGNATURE-----
On 1/23/23 05:49, Carlos E. R. wrote:
cer@Telcontar:~> sudo /usr/sbin/iotop -o -d 3.3333
Total DISK READ : 1169.77 K/s | Total DISK WRITE : 12.79 K/s Actual DISK READ: 1168.61 K/s | Actual DISK WRITE: 48.84 K/s TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND 2041 be/4 news 490.70 K/s 0.00 B/s ?unavailable? texpire 9622 be/4 cer 0.00 B/s 6.98 K/s ?unavailable? firefox --sm-client-id 27~-9abbeba61260 [LS Thread] 8039 idle cer 679.07 K/s 0.00 B/s ?unavailable? tracker-miner-fs-3 12912 be/4 cer 0.00 B/s 5.81 K/s ?unavailable? firefox --sm-client-id 27~beba61260 [IndexedDB #45] * *
...
CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO %
That is strange, confirmed with 5.14.21-150400.24.38-default as well on 15.4. Would be worth knowing whether enabling the option comes with any downside -- if not, why doesn't the kernel have it enabled? Moreover, how did it go this long without being noticed? -- David C. Rankin, J.D.,P.E.
On 2023-01-24 04:15, David C. Rankin wrote:
On 1/23/23 05:49, Carlos E. R. wrote:
cer@Telcontar:~> sudo /usr/sbin/iotop -o -d 3.3333
Total DISK READ : 1169.77 K/s | Total DISK WRITE : 12.79 K/s Actual DISK READ: 1168.61 K/s | Actual DISK WRITE: 48.84 K/s TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND 2041 be/4 news 490.70 K/s 0.00 B/s ?unavailable? texpire 9622 be/4 cer 0.00 B/s 6.98 K/s ?unavailable? firefox --sm-client-id 27~-9abbeba61260 [LS Thread] 8039 idle cer 679.07 K/s 0.00 B/s ?unavailable? tracker-miner-fs-3 12912 be/4 cer 0.00 B/s 5.81 K/s ?unavailable? firefox --sm-client-id 27~beba61260 [IndexedDB #45] * *
...
CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO %
That is strange, confirmed with 5.14.21-150400.24.38-default as well on 15.4. Would be worth knowing whether enabling the option comes with any downside -- if not, why doesn't the kernel have it enabled?
Moreover, how did it go this long without being noticed?
Not that long, I know I used it maybe two months ago and it worked. I don't remember if that was on Leap 15.3 or 15.4, though. I will report in Bugzilla, time permitting. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-01-24 11:25, Carlos E. R. wrote:
On 2023-01-24 04:15, David C. Rankin wrote:
On 1/23/23 05:49, Carlos E. R. wrote:
cer@Telcontar:~> sudo /usr/sbin/iotop -o -d 3.3333
Total DISK READ : 1169.77 K/s | Total DISK WRITE : 12.79 K/s Actual DISK READ: 1168.61 K/s | Actual DISK WRITE: 48.84 K/s TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND 2041 be/4 news 490.70 K/s 0.00 B/s ?unavailable? texpire 9622 be/4 cer 0.00 B/s 6.98 K/s ?unavailable? firefox --sm-client-id 27~-9abbeba61260 [LS Thread] 8039 idle cer 679.07 K/s 0.00 B/s ?unavailable? tracker-miner-fs-3 12912 be/4 cer 0.00 B/s 5.81 K/s ?unavailable? firefox --sm-client-id 27~beba61260 [IndexedDB #45] * *
...
CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO %
That is strange, confirmed with 5.14.21-150400.24.38-default as well on 15.4. Would be worth knowing whether enabling the option comes with any downside -- if not, why doesn't the kernel have it enabled?
Moreover, how did it go this long without being noticed?
Not that long, I know I used it maybe two months ago and it worked. I don't remember if that was on Leap 15.3 or 15.4, though.
I will report in Bugzilla, time permitting.
I forgot to report back. The bugzilla was <https://bugzilla.opensuse.org/show_bug.cgi?id=1207761> Lots of info here: <https://superuser.com/questions/610581/iotop-complains-config-task-delay-acct-not-enabled-in-kernel-only-for-specific> Kernel commit that did this: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i... delayacct: Default disabled Assuming this stuff isn't actually used much; disable it by default and avoid allocating and tracking the task_delay_info structure. You can revert this by changing the boot line in /etc/default/grub (add "delayacct"). Alternatively, run as root sysctl kernel.task_delayacct=1 when needed (in run time). It is said it can effect performance somewhat. You could call iotop with a script: #!/bin/bash # This script enables task delay accounting in the Linux kernel, runs iotop, # then on exit sets task_delayacct back to 0. # Disable task delay accounting when the script exits disable_task_delayacct() { sudo sysctl kernel.task_delayacct=0 } # Trap the EXIT signal to call the disable_task_delayacct function trap 'disable_task_delayacct' EXIT # Enable task delay accounting sudo sysctl kernel.task_delayacct=1 # Run iotop with administrative privileges sudo iotop -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
participants (2)
-
Carlos E. R. -
David C. Rankin