[regression] lingering pvscan during boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lvm2 (Ubuntu) |
Confirmed
|
High
|
Eric Desrochers |
Bug Description
Since lvm2 was updated to 2.02.176-
On the affected servers, this is visible as there are 2 instances of systemd-udevd, one in the init.scope and another in system.slice:
$ systemd-cgls | cat
Control group /:
-.slice
├─user.slice
│ ├─user-501.slice
│ │ ├─session-7.scope
│ │ │ ├─12324 sshd: foo [priv]
│ │ │ ├─12353 sshd: foo@pts/2
│ │ │ ├─12354 script --quiet --return --command /bin/bash -l /dev/null
│ │ │ ├─12356 /bin/bash -l
│ │ │ ├─12375 sudo -i
│ │ │ └─12385 -bash
│ │ └─user@501.service
│ │ └─init.scope
│ │ ├─12326 /lib/systemd/
│ │ └─12327 (sd-pam)
│ └─user-500.slice
│ ├─user@500.service
│ │ └─init.scope
│ │ ├─12185 /lib/systemd/
│ │ └─12186 (sd-pam)
│ └─session-3.scope
│ ├─12170 sshd: sdeziel [priv]
│ ├─12254 sshd: sdeziel@pts/0
│ ├─12255 script --quiet --return --command /bin/bash -l /dev/null
│ ├─12257 /bin/bash -l
│ ├─14409 systemd-cgls
│ └─14410 cat
├─init.scope
│ ├─ 1 /sbin/init kaslr nosplash
│ ├─1451 /lib/systemd/
│ ├─1466 /sbin/lvm pvscan --cache --activate ay --major 8 --minor 3
│ ├─1470 /sbin/lvm pvscan --cache --activate ay --major 8 --minor 2
│ ├─1481 /sbin/lvm pvscan --cache --activate ay --major 253 --minor 1
│ └─1551 /sbin/lvm pvscan --cache --activate ay --major 253 --minor 1
└─system.slice
├─irqbalance.
│ └─2796 /usr/sbin/
├─systemd-
│ └─2833 /lib/systemd/
├─systemd-
│ └─1627 /lib/systemd/
├─cron.service
│ ├─ 2786 /usr/sbin/cron -f
│ └─12308 /usr/bin/python /usr/sbin/
├─system-
│ └─<email address hidden>
│ └─12112 /sbin/agetty -o -p -- \u --keep-baud 115200,38400,9600 ttyS0 vt220
├─systemd-
│ └─1601 /lib/systemd/
├─ssh.service
│ └─12115 /usr/sbin/sshd -D
├─rsyslog.service
│ └─2781 /usr/sbin/rsyslogd -n
├─nagios-
│ └─12108 /usr/sbin/nrpe -c /etc/nagios/
├─lvm2-
│ └─1630 /sbin/lvmetad -f
├─systemd-
│ └─3280 /lib/systemd/
├─dbus.service
│ └─2762 /usr/bin/
├─systemd-
│ └─2491 /lib/systemd/
├─system-
│ └─<email address hidden>
│ └─12113 /sbin/agetty -o -p -- \u --noclear tty1 linux
├─systemd-
│ └─2797 /lib/systemd/
└─ganeti.service
├─ 3892 /usr/sbin/
├─12173 /usr/sbin/
└─12276 /usr/sbin/
The systemd-udevd in init.scope and the many /sbin/lvm pvscan it launched during boot are left there forever.
This trips our monitoring for binaries using deleted binaries/libs and is also visible like that:
# pgrep systemd-udevd
1451
1627
# ls -l /proc/1451/exe
lrwxrwxrwx 1 root root 0 Feb 19 10:35 /proc/1451/exe -> '/lib/systemd/
# ls -l /proc/1627/exe
lrwxrwxrwx 1 root root 0 Feb 19 10:35 /proc/1627/exe -> /lib/systemd/
This can be compared with another server *NOT AFFECTED*, where the init.scope is cleaner (/sbin/init only) and a single systemd-udevd process:
# systemd-cgls | cat
Control group /:
-.slice
├─user.slice
│ └─user-0.slice
│ ├─session-313.scope
│ │ ├─90332 sshd: root@pts/0
│ │ ├─90406 script --quiet --return --command /bin/bash -l /dev/null
│ │ ├─90410 /bin/bash -l
│ │ ├─90436 systemd-cgls
│ │ └─90437 cat
│ └─user@0.service
│ └─init.scope
│ ├─90334 /lib/systemd/
│ └─90335 (sd-pam)
├─init.scope
│ └─1 /sbin/init kaslr nosplash
└─system.slice
...
├─systemd-
│ └─2622 /lib/systemd/
...
├─lvm2-
│ └─2621 /sbin/lvmetad -f
...
Additional information:
# lsb_release -rd
Description: Ubuntu 18.04.4 LTS
Release: 18.04
# apt-cache policy lvm2 systemd
lvm2:
Installed: 2.02.176-
Candidate: 2.02.176-
Version table:
*** 2.02.176-
500 http://
100 /var/lib/
2.
500 http://
systemd:
Installed: 237-3ubuntu10.39
Candidate: 237-3ubuntu10.39
Version table:
*** 237-3ubuntu10.39 500
500 http://
100 /var/lib/
237-
500 http://
237-3ubuntu10 500
500 http://
Eric, this is reported as a regression in an SRU you did, can you please follow through?