Description of problem: When executing iotop, SWAPIN and IO % data is not shown. This error appears: "CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO %" Version-Release number of selected component (if applicable): How reproducible: executing iotop command Steps to Reproduce: directly executing iotop command with root user: # iotop
Thank you for the report, which I confirm: Total DISK READ : 0.00 B/s | Total DISK WRITE : 0.00 B/s Actual DISK READ: 0.00 B/s | Actual DISK WRITE: 0.00 B/s TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND 1 be/4 root 0.00 B/s 0.00 B/s ?unavailable? init 2 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [kthreadd] 3 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [rcu_gp] 4 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [rcu_par_gp] 6 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [kworker~-kblockd] 8 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [mm_percpu_wq] 9 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [rcu_tasks_rude_] 10 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [rcu_tasks_trace] 11 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [ksoftirqd/0] 12 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [rcu_sched] 13 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [migration/0] 14 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [idle_inject/0] 15 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [cpuhp/0] 16 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [cpuhp/1] 17 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [idle_inject/1] 18 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [migration/1] 19 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [ksoftirqd/1] 21 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [kworker~_highpri] 22 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [kdevtmpfs] CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO % 24 be/4 root 0.00 B/s 0.00 B/s ?unavailable? [inet_frag_wq] Assigning this to kernel as looking most relevant. ('iotop' itself has no specific maintainer).
Summary: error showing SWAPIN and IO % data in iotop => error showing SWAPIN and IO % data in 'iotop': CONFIG_TASK_DELAY_ACCT not enabled in kernelAssignee: bugsquad => kernel
It was changed in Kernel last year for a reason: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e4042ad492357fa995921376462b04a025dd53b6 Workaround described here: https://superuser.com/questions/610581/iotop-complains-config-task-delay-acct-not-enabled-in-kernel-only-for-specific Adding "delayacct" to grub command line
Yep. the kernel parameter is needed if you want the feature
Status: NEW => RESOLVEDResolution: (none) => INVALID
thank you for your help, i will try the workaround