Erhöhte CPU-Idle Last nach Upgrade auf Proxmox 6.0

qubeck

New Member
Jul 11, 2019
2
0
1
42
Hallo,

nach Upgrade auf Proxmox 6.0 muss ich eine erhöhte CPU-Idle last feststellen.
Offenbar wird diese von udisksd/udev/systemd... durch permanente change events verursacht.

Das folgende stellt die Situation bei einem aktiven alpine 3.9 Container dar.
Der Container selbst wurde zuvor zum verifizieren frisch mit default Einstellungen angelegt.

Die Flut an "change" beginnt unmittelbar nach dem Start des Containers und hört dabei nicht auf
egal ob das rootfs mittels loop device oder vom lvm kommt.

Erst nach dem stoppen des Containers tritt im loop device fall das verhalten nicht mehr auf.
Bei lvm Quelle änderst sich die Situation auch nach dem stoppen des Containers nicht.

Ggf. ist dieser Umstand bereits bekannt falls nicht würde ich gern erörtern was die Ursache hierfür sein könnte.

top:
Code:
  601 root      20   0  654172 195632  11048 S  35,1   2,4   6:38.83 udisksd
14747 root      20   0   23828   3560   1944 S  13,2   0,0   0:05.17 systemd-udevd
  391 root      20   0   23892   5616   4120 S  11,9   0,1   2:51.04 systemd-udevd
  602 message+  20   0    9928   4948   3856 S   9,9   0,1   3:30.28 dbus-daemon
    1 root      20   0  105968  11116   7772 S   5,3   0,1   1:59.57 systemd
  609 root      20   0   19708   7572   6484 S   4,3   0,1   1:15.69 systemd-logind
17094 qu        20   0   21520   9488   7772 S   1,7   0,1   0:29.87 systemd


udevadm monitor -p (bei rootfs auf lvm):
Code:
UDEV  [169099.888185] change   /devices/virtual/block/dm-4 (block)
ACTION=change
DEVPATH=/devices/virtual/block/dm-4
SUBSYSTEM=block
SYNTH_UUID=0
DEVNAME=/dev/dm-4
DEVTYPE=disk
SEQNUM=212589
USEC_INITIALIZED=169057587546
DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG=1
DM_UDEV_PRIMARY_SOURCE_FLAG=1
DM_UDEV_RULES=1
DM_UDEV_RULES_VSN=2
DM_NAME=vmdata-vm--100--disk--0
DM_UUID=LVM-ejBMaUfqhoeZAvn6pc3PL56fKbt8KZ0cT2LkzCndJUcGllVTjbtBt4QKhgdXXNqL
DM_SUSPENDED=0
DM_VG_NAME=vmdata
DM_LV_NAME=vm-100-disk-0
DM_LV_LAYER=
ID_FS_UUID=28926ba3-5d8b-48c1-a152-5fc0a40c1eed
ID_FS_UUID_ENC=28926ba3-5d8b-48c1-a152-5fc0a40c1eed
ID_FS_VERSION=1.0
ID_FS_TYPE=ext4
ID_FS_USAGE=filesystem
.ID_FS_TYPE_NEW=ext4
MAJOR=253
MINOR=4
DEVLINKS=/dev/mapper/vmdata-vm--100--disk--0 /dev/disk/by-id/dm-name-vmdata-vm--100--disk--0 /dev/disk/by-id/dm-uuid-LVM-ejBMaUfqhoeZAvn6pc3PL56fKbt8KZ0cT2LkzCndJUcGllVTjbtBt4QKhgdXXNqL /dev/vmdata/vm-100-disk-0 /dev/disk/by-uuid/28926ba3-5d8b-48c1-a152-5fc0a40c1eed
TAGS=:systemd:

KERNEL[169099.900652] change   /devices/virtual/block/dm-4 (block)
ACTION=change
DEVPATH=/devices/virtual/block/dm-4
SUBSYSTEM=block
SYNTH_UUID=0
DEVNAME=/dev/dm-4
DEVTYPE=disk
SEQNUM=212590
MAJOR=253
MINOR=4

UDEV  [169099.906553] change   /devices/virtual/block/dm-4 (block)
ACTION=change
DEVPATH=/devices/virtual/block/dm-4
SUBSYSTEM=block
SYNTH_UUID=0
DEVNAME=/dev/dm-4
DEVTYPE=disk
SEQNUM=212590
USEC_INITIALIZED=169057587546
DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG=1
DM_UDEV_PRIMARY_SOURCE_FLAG=1
DM_UDEV_RULES=1
DM_UDEV_RULES_VSN=2
DM_NAME=vmdata-vm--100--disk--0
DM_UUID=LVM-ejBMaUfqhoeZAvn6pc3PL56fKbt8KZ0cT2LkzCndJUcGllVTjbtBt4QKhgdXXNqL
DM_SUSPENDED=0
DM_VG_NAME=vmdata
DM_LV_NAME=vm-100-disk-0
DM_LV_LAYER=
ID_FS_UUID=28926ba3-5d8b-48c1-a152-5fc0a40c1eed
ID_FS_UUID_ENC=28926ba3-5d8b-48c1-a152-5fc0a40c1eed
ID_FS_VERSION=1.0
ID_FS_TYPE=ext4
ID_FS_USAGE=filesystem
.ID_FS_TYPE_NEW=ext4
MAJOR=253
MINOR=4
DEVLINKS=/dev/disk/by-uuid/28926ba3-5d8b-48c1-a152-5fc0a40c1eed /dev/vmdata/vm-100-disk-0 /dev/mapper/vmdata-vm--100--disk--0 /dev/disk/by-id/dm-uuid-LVM-ejBMaUfqhoeZAvn6pc3PL56fKbt8KZ0cT2LkzCndJUcGllVTjbtBt4QKhgdXXNqL /dev/disk/by-id/dm-name-vmdata-vm--100--disk--0
TAGS=:systemd:

KERNEL[169099.918961] change   /devices/virtual/block/dm-4 (block)
ACTION=change
DEVPATH=/devices/virtual/block/dm-4
SUBSYSTEM=block
SYNTH_UUID=0
DEVNAME=/dev/dm-4
DEVTYPE=disk
SEQNUM=212591
MAJOR=253
MINOR=4


udevadm monitor -p (bei rootfs im fs):
Code:
UDEV  [169544.652613] change   /devices/virtual/block/loop0 (block)
ACTION=change
DEVPATH=/devices/virtual/block/loop0
SUBSYSTEM=block
SYNTH_UUID=0
DEVNAME=/dev/loop0
DEVTYPE=disk
SEQNUM=224296
USEC_INITIALIZED=2361608
ID_FS_UUID=9430e943-480b-4d8f-ae81-fffdcc184fbd
ID_FS_UUID_ENC=9430e943-480b-4d8f-ae81-fffdcc184fbd
ID_FS_VERSION=1.0
ID_FS_TYPE=ext4
ID_FS_USAGE=filesystem
.ID_FS_TYPE_NEW=ext4
MAJOR=7
MINOR=0
DEVLINKS=/dev/disk/by-uuid/9430e943-480b-4d8f-ae81-fffdcc184fbd
TAGS=:systemd:

KERNEL[169544.666657] change   /devices/virtual/block/loop0 (block)
ACTION=change
DEVPATH=/devices/virtual/block/loop0
SUBSYSTEM=block
SYNTH_UUID=0
DEVNAME=/dev/loop0
DEVTYPE=disk
SEQNUM=224297
MAJOR=7
MINOR=0

UDEV  [169544.668980] change   /devices/virtual/block/loop0 (block)
ACTION=change
DEVPATH=/devices/virtual/block/loop0
SUBSYSTEM=block
SYNTH_UUID=0
DEVNAME=/dev/loop0
DEVTYPE=disk
SEQNUM=224297
USEC_INITIALIZED=2361608
ID_FS_UUID=9430e943-480b-4d8f-ae81-fffdcc184fbd
ID_FS_UUID_ENC=9430e943-480b-4d8f-ae81-fffdcc184fbd
ID_FS_VERSION=1.0
ID_FS_TYPE=ext4
ID_FS_USAGE=filesystem
.ID_FS_TYPE_NEW=ext4
MAJOR=7
MINOR=0
DEVLINKS=/dev/disk/by-uuid/9430e943-480b-4d8f-ae81-fffdcc184fbd
TAGS=:systemd:

KERNEL[169544.683502] change   /devices/virtual/block/loop0 (block)
ACTION=change
DEVPATH=/devices/virtual/block/loop0
SUBSYSTEM=block
SYNTH_UUID=0
DEVNAME=/dev/loop0
DEVTYPE=disk
SEQNUM=224298
MAJOR=7
MINOR=0
 
can reproduce here once I install udisks2 - which is not part of the default install. do you use it for anything? if not, removing it is probably a good idea ;)
 
Well, that's interesting. Thanks for analyzing!

Removing that would the whole "gvfs" support. I do need it on that particular machine from time to time, I'll see what I can do...
 
if you can reproduce it using stock Debian Buster + Debian's lxc, it's probably worth it to file a bug (e.g., using "reportbug udisks2")
 
Hoping this thread isn't too old.. this same issue is happening to me on Proxmox 6.0-7 Debian Buster + LXC, and is reproducible with a reboot or simply restarting either of my LXCs. I'm not sure what info I should provide here or if/when I file a bug, but this is what I see when I run udevadm monitor and it will do this infinitely until I systemctl restart systemd-udevd. Any help would be much appreciated!

Code:
KERNEL[43.917104] change   /devices/virtual/block/loop0 (block)
UDEV  [43.924839] change   /devices/virtual/block/loop0 (block)
KERNEL[43.927861] change   /devices/virtual/block/loop1 (block)
UDEV  [43.934808] change   /devices/virtual/block/loop1 (block)
KERNEL[43.939621] change   /devices/virtual/block/loop0 (block)
UDEV  [43.946940] change   /devices/virtual/block/loop0 (block)
KERNEL[43.948095] change   /devices/virtual/block/loop1 (block)
UDEV  [43.954792] change   /devices/virtual/block/loop1 (block)
KERNEL[43.961635] change   /devices/virtual/block/loop0 (block)
UDEV  [43.969086] change   /devices/virtual/block/loop0 (block)
KERNEL[43.971906] change   /devices/virtual/block/loop1 (block)
UDEV  [43.979408] change   /devices/virtual/block/loop1 (block)
KERNEL[43.987316] change   /devices/virtual/block/loop0 (block)
UDEV  [43.995598] change   /devices/virtual/block/loop0 (block)
KERNEL[43.998095] change   /devices/virtual/block/loop1 (block)
UDEV  [44.006131] change   /devices/virtual/block/loop1 (block)
KERNEL[44.014264] change   /devices/virtual/block/loop0 (block)
UDEV  [44.023125] change   /devices/virtual/block/loop0 (block)
KERNEL[44.023838] change   /devices/virtual/block/loop1 (block)
UDEV  [44.032961] change   /devices/virtual/block/loop1 (block)


EDIT: I do have udisks2 installed, although I'm not entirely sure how that got installed. Looking through dpkg logs it was installed at the same time I installed exfat-utils a couple months back, but it's not a dependency. Really not sure why it was installed or if it's needed at this point.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!