--- Comment #7 from Thiago Macieira <thiago(a)kde.org> ---
(In reply to zhen ren from comment #6)
I can replicate this locally now;-)
I can confirm that the message "WARNING: There are still devices being
monitored." comes from dmeventd (the string is in the /usr/sbin/dmeventd
executable). I can confirm that the dmeventd process is running after boot.
According to "man dmeventd", it will be started to run when
mirror/raid/snapshot/thin feature(s) is/are used. In your case, it's "thin
pool" - system-pool0-tpool being monitored. The time when we create/activate
a thin pool is good chance to start this deamon, which can be done within
the code of LVM tools' commands.
Enabling the "dm-event.service" explicitly works for me. Could you have a
# systemctl enable dm-event.service
Created symlink from /etc/systemd/system/sysinit.target.wants/dm-event.service
It's enabled now. I'll let you know after my next reboot how it goes
take long, this machine crashes on suspend and on hibernate very often).
You are receiving this mail because:
You are on the CC list for the bug.