Search results

  1. D

    wearout indicator

    Hi. I've just paid attention that wearout indicator shows incorrect values. When smartctl was shown 10% indicator in pve was shown 0%. Now it's 1% while the real is 11%. See attached pic. PVE Manager Version is 5.4-15/d0ec33c6
  2. D

    iowait time (wa) in lxc after PVE dist upgrade

    I think I found the topic with related trouble. Will follow it.
  3. D

    iowait time (wa) in lxc after PVE dist upgrade

    So, how can I fix this behaviour? htop for example have no iowait display option on the lxc containers at all! top remains zero =((( It is very important parameter for monitoring... I even tried to cat /proc/stat and see zero value at the 5th place (it shows the amount of time the CPU has spent...
  4. D

    iowait time (wa) in lxc after PVE dist upgrade

    I've just checked privileged and unprivileged fresh deployed containers on Archlinux, Debian 9, Ubuntu 16 and openSuse 15.1 on two nodes of cluster - wa is zero.
  5. D

    iowait time (wa) in lxc after PVE dist upgrade

    I'll try on the other distrib and post the result. thanks. And yes, I still see io stats on the PVE GUI
  6. D

    iowait time (wa) in lxc after PVE dist upgrade

    Unprivileged. Yes, it affects all containers (Ubuntu 18.04). Nothing unusual in log on host or container. The only error in log on the containers: Dec 23 19:45:49 ns2 systemd[1]: Failed to reset devices.list on /user.slice: Operation not permitted
  7. D

    iowait time (wa) in lxc after PVE dist upgrade

    Yes, of course. I see the same issue on 2 nodes of cluster. PVE Manager Version pve-manager/5.4-13/aee6f0ec
  8. D

    iowait time (wa) in lxc after PVE dist upgrade

    Hello. I've just found out, that iowait time (wa in top) parameter in the lxc containers remains zero value just after I've upgraded PVE from 5.3-8 to 5.4-13. Is it a bug or a feature? wa in the host system and in kvm virtual machines shows correctly. See attached screenshot of one of my lxc...