[opensuse-support] kernel removal
Hi, Still getting a collection of kernels.....can I just use zypper to remove them ?? mike -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Op donderdag 30 januari 2020 00:41:41 CET schreef mike:
What do you call a collection of kernels? Please show rpm -qa | grep kernel-default -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 1/29/20 6:45 PM, Knurpht-openSUSE wrote:
well I have vmlinuz-5.4.7, vmlinuz-5.4.10, vmlinuz-5.4.12,vmlinuz-5.4.13, vmlinuz-5.4.14
rpm -qa | grep kernel-default
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* mike <furryllama@comcast.net> [01-29-20 18:43]:
certainly, or rpm -e kernel-default-5.4.10-1.1.x86_64 or systemctl start purge-kernels.service (but you must have the number of kernels you want to retain set or it will remove all but present and last) or you could manually delete them provided you know which and after you update the rpmdb -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* mike <furryllama@comcast.net> [01-29-20 19:31]:
IF, IF, IF you are confident in your approach, but would be much safer to: zypper -v rm -u vmlinuz-5.4.8 vmlinuz-5.4.10 vmlinuz-5.4.11 **PROVIDED** you are confident ... zypper will not complete the operation until it tells you what it will do and waits for confirmation that this IS what you want to do. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 1/29/20 8:31 PM, Patrick Shanahan wrote:
OK Patrick I used this approach because the small number of kernels. I checked /boot after and they were gone. As far as I know the modules stay with the system so all should be good, and there is nothing else. I thought I read here others were having problems with the tumbleweed purge-kernels......then I rebuilt the rpm database and ran mkconfig-grub2 -o /boot/grub2/grub.cfg to update the grub menu then updatedb.to update the locate files database......thanks for the help.......
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 1/29/20 5:41 PM, mike wrote:
The "purge-kernels" service is currently broken in Tumbleweed. https://lists.opensuse.org/opensuse-factory/2020-01/msg00258.html You can use: zypper purge-kernels to do it manually. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Thursday, January 30, 2020 9:49:17 AM WIB mike wrote:
Have followed the ongoing discusion with interrest because I have more or less the same problem. I have the following default kernels: *kernel-default*-5.3.12-2.2.x86_64 *kernel-default*-5.4.7-1.1.x86_64 *kernel-default*-5.3.12-1.1.x86_64 *kernel-default*-5.4.12-1.1.x86_64 *kernel-default*-5.4.10-1.1.x86_64 *kernel-default*-5.4.13-1.1.x86_64 *kernel-default*-5.4.14-1.1.x86_64 None of the mentioned solutions to clean up my mess works up to now. "rpm -e kernel-default-5etc.will end with a complaint about the rpm.lock. "zypper purge-kernels" starts and ends after 5% and does not proceed from there. What would be my next move in order the get the kernel problem to an end. could I somehow overcome the rpm lock? -- opensuse:tumbleweed:20200128 Qt: 5.14.0 KDE Frameworks: 5.66.0 - KDE Plasma: 5.17.5 - kwin 5.17.5 kmail2 5.13.1 (19.12.1) - akonadiserver 5.13.1 (19.12.1) - Kernel: 5.4.7-1-default - xf86- video-nouveau:
Am Freitag, 31. Januar 2020, 07:25:52 CET schrieb Cons Brouerius van Nidek:
I can at least report that zypper purge-kernels worked smart for me. You may want to theck the directory /.snapshots/ for some 'abandoned' snapshots. I had an old one in there that blocked some 10 GB space and preserved some old kernels, but was not shown in snapper list HTH Axel -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Friday, January 31, 2020 1:33:04 PM WIB Axel Braun wrote:
Same here. Two snapshots which do not show in the snapper list. But how can I delete them. Snapper delete does not find them and my midnicht commander does not want to delete this kind of files. How did you got rid of the noshows? Thanks for the tip. Can now point to something which should not be there Thanks, Constant>
HTH Axel
-- opensuse:tumbleweed:20200128 Qt: 5.14.0 KDE Frameworks: 5.66.0 - KDE Plasma: 5.17.5 - kwin 5.17.5 kmail2 5.13.1 (19.12.1) - akonadiserver 5.13.1 (19.12.1) - Kernel: 5.4.7-1- default - xf86-video-nouveau: -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Fri, Jan 31, 2020 at 12:47 PM Cons Brouerius van Nidek <constant@indo.net.id> wrote:
snapshots cannot "preserve old kernels" that you see in rpm list
btrfs subvolume delete -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Am Freitag, 31. Januar 2020, 10:47:25 CET schrieb Cons Brouerius van Nidek:
rm -rf /.snapshots/<abandoned snapshot> worked well for me @Andrej:
snapshots cannot "preserve old kernels" that you see in rpm list
May be. But afterwards all the old kernels got purged automatically Cheers Axel -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Cons Brouerius van Nidek wrote:
What message exactly? Can you not just remove that lock file (as root)?
"zypper purge-kernels" starts and ends after 5% and does not proceed from there.
It might re-run dracut, which can take a while. How long did you wait? Any other messages in the syslog? I have changed my /usr/lib/systemd/system/purge-kernels.service to ExecStart=/usr/bin/zypper --non-interactive purge-kernels and it did successfully remove my old kernels on last boot....
What would be my next move in order the get the kernel problem to an end.
could I somehow overcome the rpm lock?
It probably is /var/lib/rpm/.rpm.lock, but that should be mentioned in the error message, no? And you *do* have to run it as root/via sudo of course. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Op vrijdag 31 januari 2020 14:17:28 CET schreef mike:
You'd have to remove them before doing what you did. -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Cons Brouerius van Nidek <constant@indo.net.id> [01-31-20 01:27]:
as root: zypper -v rm -u kernel-default-5.3.* kernel-default-5.4.7* \ kernel-default-5.4.10* kernel-default-5.4.12* will keep only 5.4.13 and 5.4.14 you can as root employ purge-kernels by the example your were provided earlier in the thread: zypper purge-kernels which will apply as prescribed in /etc/zypp/zypp.conf:multiversion.kernels -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 31/01/2020 07.25, Cons Brouerius van Nidek wrote: | Have followed the ongoing discusion with interrest because I have | more or less the same problem. | | I have the following default kernels: | | kernel-default-5.3.12-2.2.x86_64 kernel-default-5.4.7-1.1.x86_64 | kernel-default-5.3.12-1.1.x86_64 kernel-default-5.4.12-1.1.x86_64 | kernel-default-5.4.10-1.1.x86_64 kernel-default-5.4.13-1.1.x86_64 | kernel-default-5.4.14-1.1.x86_64 | | None of the mentioned solutions to clean up my mess works up to | now. | | "rpm -e kernel-default-5etc.will end with a complaint about the | rpm.lock. Well, this is your problem. But what "lock" are you talking about? It may be the rpm database lock, in which case the solution is to verify that *nothing* is running that can access the rpm database (no yast, no zypper, no packagekit manager, etc), and then delete the lock file. The timestamp on the file may give a hint. Or it can be a package lock, in which case you have to decide if you want to keep or delete it. You have not posted the exact error message you get, anyway... - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXjRojwAKCRC1MxgcbY1H 1b2TAJ0Sa6zUxft3M3/30yk/BTX8TzUMFQCglDql3XJVwun1LNNdBc0h8zkdxrY= =NrNX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 1/29/20 6:41 PM, mike wrote:
I'm kinda surprised this hasn't been mentioned yet . . . In zypp.conf you can specify the number of kernels you want the system to keep (there are ~half-dozen variables you can use; the very easy syntax is explained in the file). You can also of course remove them with zypper but I have found it easier to just run YaST Software and select those I want deleted. --dg -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Op donderdag 30 januari 2020 00:41:41 CET schreef mike:
What do you call a collection of kernels? Please show rpm -qa | grep kernel-default -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 1/29/20 6:45 PM, Knurpht-openSUSE wrote:
well I have vmlinuz-5.4.7, vmlinuz-5.4.10, vmlinuz-5.4.12,vmlinuz-5.4.13, vmlinuz-5.4.14
rpm -qa | grep kernel-default
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* mike <furryllama@comcast.net> [01-29-20 18:43]:
certainly, or rpm -e kernel-default-5.4.10-1.1.x86_64 or systemctl start purge-kernels.service (but you must have the number of kernels you want to retain set or it will remove all but present and last) or you could manually delete them provided you know which and after you update the rpmdb -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* mike <furryllama@comcast.net> [01-29-20 19:31]:
IF, IF, IF you are confident in your approach, but would be much safer to: zypper -v rm -u vmlinuz-5.4.8 vmlinuz-5.4.10 vmlinuz-5.4.11 **PROVIDED** you are confident ... zypper will not complete the operation until it tells you what it will do and waits for confirmation that this IS what you want to do. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 1/29/20 8:31 PM, Patrick Shanahan wrote:
OK Patrick I used this approach because the small number of kernels. I checked /boot after and they were gone. As far as I know the modules stay with the system so all should be good, and there is nothing else. I thought I read here others were having problems with the tumbleweed purge-kernels......then I rebuilt the rpm database and ran mkconfig-grub2 -o /boot/grub2/grub.cfg to update the grub menu then updatedb.to update the locate files database......thanks for the help.......
-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (10)
-
Andrei Borzenkov -
Axel Braun -
Carlos E. R. -
Cons Brouerius van Nidek -
DennisG -
Knurpht-openSUSE -
mike -
Neil Rickert -
Patrick Shanahan -
Peter Suetterlin