/sbin/zed process keeps using 100% cpu

Feb 20, 2019
4
1
1
49
On Proxmox VE Community 5.3-9 the process /sbin/zed keeps using one cpu core at 100% either with all the VMs stopped.
Can somebody help me? I really don't know what is wrong and how to fix it.

Following the installation detail:

proxmox-ve: 5.3-1 (running kernel: 4.15.18-11-pve)
pve-manager: 5.3-9 (running version: 5.3-9/ba817b29)
pve-kernel-4.15: 5.3-2
pve-kernel-4.15.18-11-pve: 4.15.18-33
pve-kernel-4.15.18-10-pve: 4.15.18-32
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-46
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-38
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-33
pve-container: 2.0-34
pve-docs: 5.3-2
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-17
pve-firmware: 2.0-6
pve-ha-manager: 2.0-6
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 3.10.1-1
qemu-server: 5.0-46
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3

proxmox.jpg

Thank you in advance.
 
The ZFS Event Daemon (zed) is in the systemd unit zfs-zed, so to restart it you have to use:
Code:
systemctl restart zfs-zed
The path to the zed executable is strange, in fact I have
Code:
$ systemctl status zfs-zed

● zfs-zed.service - ZFS Event Daemon (zed)
   Loaded: loaded (/lib/systemd/system/zfs-zed.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-02-20 17:01:13 CET; 24s ago
     Docs: man:zed(8)
 Main PID: 6421 (zed)
    Tasks: 3 (limit: 4915)
   Memory: 660.0K
      CPU: 3ms
   CGroup: /system.slice/zfs-zed.service
           └─6421 /usr/sbin/zed -F

Feb 20 17:01:13 pve-test systemd[1]: Started ZFS Event Daemon (zed).
Feb 20 17:01:13 pve-test zed[6421]: ZFS Event Daemon 0.7.12-pve1~bpo1 (PID 6421)
Feb 20 17:01:13 pve-test zed[6421]: Processing events since eid=6

In your pveversion -v I can't see the line about zfs utils version, in mine:
Code:
zfsutils-linux: 0.7.12-pve1~bpo1

If you use
Code:
apt update
apt dist-upgrade
do you see any errors?
 
The ZFS Event Daemon (zed) is in the systemd unit zfs-zed, so to restart it you have to use:
Code:
systemctl restart zfs-zed
The path to the zed executable is strange, in fact I have
Code:
$ systemctl status zfs-zed

● zfs-zed.service - ZFS Event Daemon (zed)
   Loaded: loaded (/lib/systemd/system/zfs-zed.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-02-20 17:01:13 CET; 24s ago
     Docs: man:zed(8)
 Main PID: 6421 (zed)
    Tasks: 3 (limit: 4915)
   Memory: 660.0K
      CPU: 3ms
   CGroup: /system.slice/zfs-zed.service
           └─6421 /usr/sbin/zed -F

Feb 20 17:01:13 pve-test systemd[1]: Started ZFS Event Daemon (zed).
Feb 20 17:01:13 pve-test zed[6421]: ZFS Event Daemon 0.7.12-pve1~bpo1 (PID 6421)
Feb 20 17:01:13 pve-test zed[6421]: Processing events since eid=6

In your pveversion -v I can't see the line about zfs utils version, in mine:
Code:
zfsutils-linux: 0.7.12-pve1~bpo1

If you use
Code:
apt update
apt dist-upgrade
do you see any errors?


Seems like I have an old zfsutils-linux version.
This is my zed status output:

Code:
root@vm-1:~# systemctl status zfs-zed
● zfs-zed.service - ZFS Event Daemon (zed)
   Loaded: loaded (/lib/systemd/system/zfs-zed.service; static; vendor preset: enabled)
   Active: active (running) since Wed 2019-02-20 17:20:27 CET; 21min ago
     Docs: man:zed(8)
 Main PID: 27226 (zed)
    Tasks: 1 (limit: 4915)
   Memory: 408.0K
      CPU: 21min 49.615s
   CGroup: /system.slice/zfs-zed.service
           └─27226 /sbin/zed -F

Feb 20 17:20:27 vm-1 systemd[1]: Started ZFS Event Daemon (zed).
Feb 20 17:20:27 vm-1 zed[27226]: ZFS Event Daemon 0.6.5-pve6~jessie (PID 27226)
Feb 20 17:20:27 vm-1 zed[27226]: Processing events since eid=0

apt update; apt dist-upgrade di nothing, system is updated.