I found on my system that there are some more intird files created after a zypper dup when a new kernel version is installed, as installed kernels are available. When I delete the files manually, they are re-created after the next kernel update again. Can this be configured or is that a bug? ls /boot/ -l insgesamt 378608 -rw-r--r-- 1 root root 1725 15. Jan 21:48 boot.readme lrwxrwxrwx 1 root root 42 6. Feb 16:50 config-5.16.4-1-default -> ../usr/lib/modules/5.16.4-1-default/config lrwxrwxrwx 1 root root 42 9. Feb 22:53 config-5.16.5-1-default -> ../usr/lib/modules/5.16.5-1-default/config lrwxrwxrwx 1 root root 42 14. Feb 19:58 config-5.16.8-1-default -> ../usr/lib/modules/5.16.8-1-default/config -rw-r--r-- 1 root root 0 14. Feb 19:58 do_purge_kernels drwxr-xr-x 3 root root 16384 1. Jan 1970 efi drwxr-xr-x 1 root root 122 14. Feb 19:59 grub2 lrwxrwxrwx 1 root root 23 14. Feb 19:58 initrd -> initrd-5.16.8-1-default -rw------- 1 root root 31812176 13. Feb 22:59 initrd-5.10.1-1-default -rw------- 1 root root 31798596 13. Feb 22:59 initrd-5.10.12-1-default -rw------- 1 root root 31798592 13. Feb 23:00 initrd-5.10.3-1-default -rw------- 1 root root 31798592 13. Feb 23:00 initrd-5.10.4-1-default -rw------- 1 root root 31798592 13. Feb 23:01 initrd-5.10.5-1-default -rw------- 1 root root 31798593 13. Feb 23:01 initrd-5.10.7-1-default -rw------- 1 root root 31798592 13. Feb 23:01 initrd-5.10.9-1-default -rw------- 1 root root 31798593 13. Feb 23:02 initrd-5.11.6-1-default -rw------- 1 root root 44609838 13. Feb 23:02 initrd-5.16.4-1-default -rw------- 1 root root 44612500 13. Feb 23:03 initrd-5.16.5-1-default -rw------- 1 root root 43963992 14. Feb 19:59 initrd-5.16.8-1-default lrwxrwxrwx 1 root root 47 6. Feb 16:50 sysctl.conf-5.16.4-1-default -> ../usr/lib/modules/5.16.4-1-default/sysctl.conf lrwxrwxrwx 1 root root 47 9. Feb 22:53 sysctl.conf-5.16.5-1-default -> ../usr/lib/modules/5.16.5-1-default/sysctl.conf lrwxrwxrwx 1 root root 47 14. Feb 19:58 sysctl.conf-5.16.8-1-default -> ../usr/lib/modules/5.16.8-1-default/sysctl.conf lrwxrwxrwx 1 root root 46 6. Feb 16:50 System.map-5.16.4-1-default -> ../usr/lib/modules/5.16.4-1-default/System.map lrwxrwxrwx 1 root root 46 9. Feb 22:53 System.map-5.16.5-1-default -> ../usr/lib/modules/5.16.5-1-default/System.map lrwxrwxrwx 1 root root 46 14. Feb 19:58 System.map-5.16.8-1-default -> ../usr/lib/modules/5.16.8-1-default/System.map lrwxrwxrwx 1 root root 24 14. Feb 19:58 vmlinuz -> vmlinuz-5.16.8-1-default lrwxrwxrwx 1 root root 43 6. Feb 16:50 vmlinuz-5.16.4-1-default -> ../usr/lib/modules/5.16.4-1-default/vmlinuz lrwxrwxrwx 1 root root 43 9. Feb 22:53 vmlinuz-5.16.5-1-default -> ../usr/lib/modules/5.16.5-1-default/vmlinuz lrwxrwxrwx 1 root root 43 14. Feb 19:58 vmlinuz-5.16.8-1-default -> ../usr/lib/modules/5.16.8-1-default/vmlinuz
On 2022-02-14 20:03, Frank Kunz wrote:
I found on my system that there are some more intird files created after a zypper dup when a new kernel version is installed, as installed kernels are available. When I delete the files manually, they are re-created after the next kernel update again.
Can this be configured or is that a bug?
systemctl status purge-kernels.service Is it enabled? -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
Am 14.02.22 um 20:49 schrieb Carlos E. R.:
On 2022-02-14 20:03, Frank Kunz wrote:
I found on my system that there are some more intird files created after a zypper dup when a new kernel version is installed, as installed kernels are available. When I delete the files manually, they are re-created after the next kernel update again.
Can this be configured or is that a bug?
systemctl status purge-kernels.service
Is it enabled?
Yes, but it does only a cleanup of the kernels, but not the initrd: systemctl status purge-kernels.service ○ purge-kernels.service - Purge old kernels Loaded: loaded (/usr/lib/systemd/system/purge-kernels.service; enabled; vendor preset: enabled) Active: inactive (dead) since Mon 2022-02-14 20:17:43 CET; 48min ago Process: 1728 ExecStart=/usr/bin/zypper -n purge-kernels (code=exited, status=0/SUCCESS) Process: 16077 ExecStartPost=/bin/rm -f /boot/do_purge_kernels (code=exited, status=0/SUCCESS) Main PID: 1728 (code=exited, status=0/SUCCESS) CPU: 59.651s Feb 14 20:17:35 donald.fritz.box zypper[1728]: (4/5) kernel-default-devel-5.16.4-1.1.x86_64 wird entfernt [...> Feb 14 20:17:35 donald.fritz.box [RPM][15353]: Transaction ID 620aaacf started Feb 14 20:17:36 donald.fritz.box [RPM][15353]: erase kernel-devel-5.16.4-1.1.noarch: success Feb 14 20:17:39 donald.fritz.box [RPM][15353]: erase kernel-devel-5.16.4-1.1.noarch: success Feb 14 20:17:39 donald.fritz.box [RPM][15353]: Transaction ID 620aaacf finished: 0 Feb 14 20:17:39 donald.fritz.box zypper[1728]: (5/5) kernel-devel-5.16.4-1.1.noarch wird entfernt [.....fertig] Feb 14 20:17:43 donald.fritz.box zypper[1728]: Feb 14 20:17:43 donald.fritz.box systemd[1]: purge-kernels.service: Deactivated successfully. Feb 14 20:17:43 donald.fritz.box systemd[1]: Finished Purge old kernels. Feb 14 20:17:43 donald.fritz.box systemd[1]: purge-kernels.service: Consumed 59.651s CPU time.
On 2022-02-14 21:08, Frank Kunz wrote:
Am 14.02.22 um 20:49 schrieb Carlos E. R.:
On 2022-02-14 20:03, Frank Kunz wrote:
I found on my system that there are some more intird files created after a zypper dup when a new kernel version is installed, as installed kernels are available. When I delete the files manually, they are re-created after the next kernel update again.
Can this be configured or is that a bug?
systemctl status purge-kernels.service
Is it enabled?
Yes, but it does only a cleanup of the kernels, but not the initrd:
I think it should do both. What else would do it? If those files are not part of an rpm, but generated locally, a script must clear them. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
On 14. 02. 22, 20:03, Frank Kunz wrote:
I found on my system that there are some more intird files created after a zypper dup when a new kernel version is installed, as installed kernels are available. When I delete the files manually, they are re-created after the next kernel update again.
Can this be configured or is that a bug?
ls /boot/ -l insgesamt 378608 -rw-r--r-- 1 root root 1725 15. Jan 21:48 boot.readme lrwxrwxrwx 1 root root 42 6. Feb 16:50 config-5.16.4-1-default -> ../usr/lib/modules/5.16.4-1-default/config lrwxrwxrwx 1 root root 42 9. Feb 22:53 config-5.16.5-1-default -> ../usr/lib/modules/5.16.5-1-default/config lrwxrwxrwx 1 root root 42 14. Feb 19:58 config-5.16.8-1-default -> ../usr/lib/modules/5.16.8-1-default/config -rw-r--r-- 1 root root 0 14. Feb 19:58 do_purge_kernels drwxr-xr-x 3 root root 16384 1. Jan 1970 efi drwxr-xr-x 1 root root 122 14. Feb 19:59 grub2 lrwxrwxrwx 1 root root 23 14. Feb 19:58 initrd -> initrd-5.16.8-1-default -rw------- 1 root root 31812176 13. Feb 22:59 initrd-5.10.1-1-default -rw------- 1 root root 31798596 13. Feb 22:59 initrd-5.10.12-1-default -rw------- 1 root root 31798592 13. Feb 23:00 initrd-5.10.3-1-default -rw------- 1 root root 31798592 13. Feb 23:00 initrd-5.10.4-1-default -rw------- 1 root root 31798592 13. Feb 23:01 initrd-5.10.5-1-default -rw------- 1 root root 31798593 13. Feb 23:01 initrd-5.10.7-1-default -rw------- 1 root root 31798592 13. Feb 23:01 initrd-5.10.9-1-default -rw------- 1 root root 31798593 13. Feb 23:02 initrd-5.11.6-1-default
It was a bug in kernel scripts after UsrMerge until we fixed it around 5.11.6. You can remove the initrds above manually.
-rw------- 1 root root 44609838 13. Feb 23:02 initrd-5.16.4-1-default -rw------- 1 root root 44612500 13. Feb 23:03 initrd-5.16.5-1-default -rw------- 1 root root 43963992 14. Feb 19:59 initrd-5.16.8-1-default lrwxrwxrwx 1 root root 47 6. Feb 16:50 sysctl.conf-5.16.4-1-default -> ../usr/lib/modules/5.16.4-1-default/sysctl.conf lrwxrwxrwx 1 root root 47 9. Feb 22:53 sysctl.conf-5.16.5-1-default -> ../usr/lib/modules/5.16.5-1-default/sysctl.conf lrwxrwxrwx 1 root root 47 14. Feb 19:58 sysctl.conf-5.16.8-1-default -> ../usr/lib/modules/5.16.8-1-default/sysctl.conf lrwxrwxrwx 1 root root 46 6. Feb 16:50 System.map-5.16.4-1-default -> ../usr/lib/modules/5.16.4-1-default/System.map lrwxrwxrwx 1 root root 46 9. Feb 22:53 System.map-5.16.5-1-default -> ../usr/lib/modules/5.16.5-1-default/System.map lrwxrwxrwx 1 root root 46 14. Feb 19:58 System.map-5.16.8-1-default -> ../usr/lib/modules/5.16.8-1-default/System.map lrwxrwxrwx 1 root root 24 14. Feb 19:58 vmlinuz -> vmlinuz-5.16.8-1-default lrwxrwxrwx 1 root root 43 6. Feb 16:50 vmlinuz-5.16.4-1-default -> ../usr/lib/modules/5.16.4-1-default/vmlinuz lrwxrwxrwx 1 root root 43 9. Feb 22:53 vmlinuz-5.16.5-1-default -> ../usr/lib/modules/5.16.5-1-default/vmlinuz lrwxrwxrwx 1 root root 43 14. Feb 19:58 vmlinuz-5.16.8-1-default -> ../usr/lib/modules/5.16.8-1-default/vmlinuz
-- js suse labs
participants (3)
-
Carlos E. R. -
Frank Kunz -
Jiri Slaby