[opensuse] purging old kernels
I've just run into the problem of my /boot partition filling up due to multiple kernel versions, but I don't understand how to resolve it. As with all my openSUSE installations of the last few years I allotted only about 125MB to /boot having previously read that that was more than sufficient, and I've never seen any official recommendation to the contrary, but some googling now shows me that the kernel multiversioning will likely require a fair bit more space than that, which I cannot do easily given the partioning layout. I looked at the notes on this page: http://lizards.opensuse.org/tag/kernel-update/ and thought of removing the 'latest-1' element from the line 'multiversion.kernels = ' since my currently installed kernel seems to be okay. After a reboot nothing is removed from /boot. The above section in zypp.conf talks about creating a directory for multiversion definitions, but I don't know if the example file it shows can really be named 'example' or something else, and don't wish to try in case I cannot reboot. So I tried commenting out the 'multiversion = provides:multiversion(kernel)' line above that. Again, a reboot makes no difference. It seems to suggest that a change would only be applied after a kernel update, but that could take months, besides which the partition is already 100% full so a new kernel likely won't install successfully anyway. How can I purge at least one older kernel (there are currently 3) directly? There's no facility in YaST software management. I could merely remove some files in /boot that wouldn't touch other files related to those kernels and is surely not a good idea. What is the proper way to go about this? Cheers, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-11 12:49, Peter wrote:
I've just run into the problem of my /boot partition filling up due to multiple kernel versions, but I don't understand how to resolve it.
As with all my openSUSE installations of the last few years I allotted only about 125MB to /boot having previously read that that was more than sufficient, and I've never seen any official recommendation to the contrary,
Mmm. Official? Startup book: http://doc.opensuse.org/documentation/html/openSUSE/opensuse-startup/art.osu... basically what it says is let the installer choose, and by default it is only root, swap, and home. Not /boot. +++······················ Define a partition setup for openSUSE in this step. In most cases a reasonable scheme that can be accepted without change is proposed. Accept the proposal with Next and proceed with the installation. Experienced users can also customize the proposal (Edit Partition Setup) or apply their own partitioning scheme (Create Partition Setup). ······················++- Reference book: http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.i... +++······················ 1.10. Suggested Partitioning¶ Define a partition setup for openSUSE in this step. In most cases a reasonable scheme that can be accepted without change is proposed. If a hard disk containing only Windows FAT or NTFS partitions is selected as the installation target, YaST proposes to shrink one of these partitions. Accept the proposal with Next and proceed with the installation. Experienced users can also customize the proposal or apply their own partitioning scheme. ······················++- http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.a... 3.1. Using the YaST Partitioner¶ There is more there, but I don't see any reference to a specific size for /boot, only to create it on some circumstances. +++······················ 3.1.2.1. Btrfs Partitioning¶ If you want to use Btrfs and Storage Administration Guide, chapter Overview of File Systems in Linux for more information on Btrfs) as your default filesystem for a newly installed system, click Partitioning on the Installation Settings screen, and check Use Btrfs as Default Filesystem. The installation system then suggests creating the /boot partition formatted with Ext3 filesystem, and the root / partition formatted with Btrfs holding a default set of subvolumes, which you can modify with the Expert Partitioner tool later. ······················++- But yes, if you ask me, 150 MB is too little. Mine are 190 and they are small. Nowdays, I would set for 1 GB, in case needs grow. I use multiversion. /etc/zypp/zypp.conf: multiversion = provides:multiversion(kernel) multiversion.kernels = latest-1,latest,running This would mean 3 kernel versions just after an update, and back to two after booting, when a systemd job (oS 12.3) kicks in and deletes at least one, those not matching the rule above. To be safe, manually delete versions when updating or before. You can reduce needed space by removing plymouth from your installation, but that's about it. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG3CS8ACgkQIvFNjefEBxoX0gCgs+fwJxiZxl0pHZjuB0yFbfZF nGYAn1S32F3PRX0WAZOfbi765nE/t/vz =gZAl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Peter wrote:
I've just run into the problem of my /boot partition filling up due to multiple kernel versions, but I don't understand how to resolve it.
As with all my openSUSE installations of the last few years I allotted only about 125MB to /boot having previously read that that was more than sufficient, and I've never seen any official recommendation to the contrary, but some googling now shows me that the kernel multiversioning will likely require a fair bit more space than that, which I cannot do easily given the partioning layout.
I guess you have specific reasons for needing a separate /boot partition?
I looked at the notes on this page: http://lizards.opensuse.org/tag/kernel-update/ and thought of removing the 'latest-1' element from the line 'multiversion.kernels = ' since my currently installed kernel seems to be okay. After a reboot nothing is removed from /boot. The above section in zypp.conf talks about creating a directory for multiversion definitions, but I don't know if the example file it shows can really be named 'example' or something else, and don't wish to try in case I cannot reboot. So I tried commenting out the 'multiversion = provides:multiversion(kernel)' line above that. Again, a reboot makes no difference. It seems to suggest that a change would only be applied after a kernel update, but that could take months, besides which the partition is already 100% full so a new kernel likely won't install successfully anyway. How can I purge at least one older kernel (there are currently 3) directly?
Use 'rm' -- Per Jessen, Zürich (19.4°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Jun 11, 2013 at 01:50:49PM +0200, Per Jessen wrote:
Peter wrote:
I've just run into the problem of my /boot partition filling up due to multiple kernel versions, but I don't understand how to resolve it.
As with all my openSUSE installations of the last few years I allotted only about 125MB to /boot having previously read that that was more than sufficient, and I've never seen any official recommendation to the contrary, but some googling now shows me that the kernel multiversioning will likely require a fair bit more space than that, which I cannot do easily given the partioning layout.
I guess you have specific reasons for needing a separate /boot partition?
I looked at the notes on this page: http://lizards.opensuse.org/tag/kernel-update/ and thought of removing the 'latest-1' element from the line 'multiversion.kernels = ' since my currently installed kernel seems to be okay. After a reboot nothing is removed from /boot. The above section in zypp.conf talks about creating a directory for multiversion definitions, but I don't know if the example file it shows can really be named 'example' or something else, and don't wish to try in case I cannot reboot. So I tried commenting out the 'multiversion = provides:multiversion(kernel)' line above that. Again, a reboot makes no difference. It seems to suggest that a change would only be applied after a kernel update, but that could take months, besides which the partition is already 100% full so a new kernel likely won't install successfully anyway. How can I purge at least one older kernel (there are currently 3) directly?
Use 'rm'
There is a service called "purge-kernels" which runs on boot by default which cleans up the multiple installed kernels. Check with "systemctl status purge-kernels". Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
I guess you have specific reasons for needing a separate /boot partition?
RAID or LVM. If RAID is used, /boot must be on a non-RAID or RAID 1 partition. With LVM, /boot must not be on LVM. If I set up a server with multiple drives, I set up LVM on RAID, with a separate partition for /boot. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
Per Jessen wrote:
I guess you have specific reasons for needing a separate /boot partition?
RAID or LVM. If RAID is used, /boot must be on a non-RAID or RAID 1 partition. With LVM, /boot must not be on LVM. If I set up a server with multiple drives, I set up LVM on RAID, with a separate partition for /boot.
Yes, I know what the reasons are, the questions was really whether the OP had those reasons. -- Per Jessen, Zürich (19.7°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Yes, I know what the reasons are, the questions was really whether the OP had those reasons.
I don't know about him, but I run LVM on my main home computer and that makes resizing /boot difficult, as it's the only non LVM partition. I'd have to redo the disk from scratch to make /boot bigger. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
James Knott wrote:
I guess you have specific reasons for needing a separate /boot partition? RAID or LVM. If RAID is used, /boot must be on a non-RAID or RAID 1
Per Jessen wrote: partition. With LVM, /boot must not be on LVM. If I set up a server with multiple drives, I set up LVM on RAID, with a separate partition for /boot.
Yes, I know what the reasons are, the questions was really whether the OP had those reasons.
Why do you need to know if someone chose that reason or another? Do you judge their fitness to have a separate boot partition based on their reason? :~/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-12 00:41, Linda Walsh wrote:
Per Jessen wrote:
Yes, I know what the reasons are, the questions was really whether the OP had those reasons.
Why do you need to know if someone chose that reason or another? Do you judge their fitness to have a separate boot partition based on their reason?
Why do you think bad of the question? I also wonder, because if he doesn't have a valid reason, he could then remove/ignore the current /boot, and move grub to "/" instead, solving the problem. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG3tA4ACgkQIvFNjefEBxoulwCfZxTcUJVXUgRVNXScacvbbLQY ZjgAn2h6I+Ncly1nODOWo/oH1m0Plo0N =txql -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Linda Walsh wrote:
Per Jessen wrote:
James Knott wrote:
I guess you have specific reasons for needing a separate /boot partition? RAID or LVM. If RAID is used, /boot must be on a non-RAID or RAID 1
Per Jessen wrote: partition. With LVM, /boot must not be on LVM. If I set up a server with multiple drives, I set up LVM on RAID, with a separate partition for /boot.
Yes, I know what the reasons are, the questions was really whether the OP had those reasons.
Why do you need to know if someone chose that reason or another? Do you judge their fitness to have a separate boot partition based on their reason?
:~/
No, only their need. If Peter had a boot-partition without needing one, he could have solved the space issue by copying /boot onto the root file system, and not mounting the boot partition at all. -- Per Jessen, Zürich (14.3°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-11 13:50, Per Jessen wrote:
Peter wrote:
Use 'rm'
Not rm. :-) Use rpm --erase whatever. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG3E7EACgkQIvFNjefEBxqIHACfRDOy4PkxKICewgCHzXLvGc81 O3wAoNzMN77qt6q/U1tpZBQHxRVmvBJg =1fEz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/11/2013 02:50 PM, Per Jessen wrote:
How can I purge at least one older kernel (there
are currently 3) directly? Use 'rm'
- just used command : rpm -qa kern* - this showed : kernel-desktop-3.8.1-30.1.i686 kernel-firmware-20130114git-2.1.noarch kernel-desktop-3.9.4-11.1.g51bf0ff.i686 .................................. - thus, if one wanted to purge : kernel-desktop-3.8.1-30.1.i686 one might command : rpm -e kernel-desktop-3.8.1-30.1.i686 ................. this will remove 3.8.1-30.1.i686 stuff from /boot directory, and, also from /lib/modules ................................ best regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
ellanios82 wrote:
rpm -qa kern*
- this showed :
kernel-desktop-3.8.1-30.1.i686 kernel-firmware-20130114git-2.1.noarch kernel-desktop-3.9.4-11.1.g51bf0ff.i686
On my system, rpm -qa|grep kernel shows: kernel-pae-devel-3.7.10-1.4.1.i686 kernel-desktop-devel-3.7.10-1.11.1.x86_64 kernel-default-devel-3.7.10-1.11.1.x86_64 kernel-default-devel-3.7.10-1.4.1.x86_64 kernel-devel-3.7.10-1.11.1.noarch kernel-pae-devel-3.7.10-1.11.1.i686 kernel-firmware-20130114git-1.2.1.noarch kernel-desktop-devel-3.7.10-1.4.1.x86_64 kernel-desktop-3.7.10-1.4.1.x86_64 kernel-desktop-3.7.10-1.11.1.x86_64 kernel-devel-3.7.10-1.4.1.noarch But /boot contains: backup_mbr initrd symvers-3.7.10-1.11-desktop.gz boot initrd-3.7.10-1.11-desktop sysctl.conf-3.7.10-1.11-desktop boot.readme lost+found System.map-3.7.10-1.11-desktop config-3.7.10-1.11-desktop message vmlinux-3.7.10-1.11-desktop.gz grub symtypes-3.7.10-1.11-default.gz vmlinuz grub2 symtypes-3.7.10-1.11-desktop.gz vmlinuz-3.7.10-1.11-desktop grub2-efi symtypes-3.7.10-1.11-pae.gz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-11 14:22, James Knott wrote:
On my system, rpm -qa|grep kernel shows:
kernel-pae-devel-3.7.10-1.4.1.i686 kernel-desktop-devel-3.7.10-1.11.1.x86_64 kernel-default-devel-3.7.10-1.11.1.x86_64 kernel-default-devel-3.7.10-1.4.1.x86_64 kernel-devel-3.7.10-1.11.1.noarch kernel-pae-devel-3.7.10-1.11.1.i686 kernel-firmware-20130114git-1.2.1.noarch kernel-desktop-devel-3.7.10-1.4.1.x86_64 kernel-desktop-3.7.10-1.4.1.x86_64 kernel-desktop-3.7.10-1.11.1.x86_64 kernel-devel-3.7.10-1.4.1.noarch
But /boot contains:
backup_mbr initrd symvers-3.7.10-1.11-desktop.gz boot initrd-3.7.10-1.11-desktop sysctl.conf-3.7.10-1.11-desktop boot.readme lost+found System.map-3.7.10-1.11-desktop config-3.7.10-1.11-desktop message vmlinux-3.7.10-1.11-desktop.gz grub symtypes-3.7.10-1.11-default.gz vmlinuz grub2 symtypes-3.7.10-1.11-desktop.gz vmlinuz-3.7.10-1.11-desktop grub2-efi symtypes-3.7.10-1.11-pae.gz
So you have 3.7.10-1.4.1 and 3.7.10-1.11.1 installed. However, /boot only has 3.7.10-1.11. It means that you have many megabytes of 3.7.10-1.4.1 still lying around which you should remove with rpm. Or leave it to system services to delete it on next update. The entire kernel is not in /boot, you know that. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG3JqAACgkQIvFNjefEBxqwugCg11L42yq4q7W1wJh2ltsz/R4L 2EAAnjWackdnFiC5C78zkjmiiBuSgB4a =l3JL -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
The entire kernel is not in /boot, you know that.
Yes, but /boot is where the space issue is. On the last kernel update, I had to free up space to let it install. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-11 15:55, James Knott wrote:
Carlos E. R. wrote:
The entire kernel is not in /boot, you know that.
Yes, but /boot is where the space issue is. On the last kernel update, I had to free up space to let it install.
Just remove the rpms. You have entries in grub that will crash. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG3MMkACgkQIvFNjefEBxpeMACbB+29L6ZBVQXJbVC3mZRsWeEH fFAAoJ5VoQGFKrRTWdES2CKlS0ujRdLE =GfEY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
Yes, but /boot is where the space issue is. On the last kernel
update, I had to free up space to let it install. Just remove the rpms. You have entries in grub that will crash.
I removed the old kernels from the boot menu. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-11 16:18, James Knott wrote:
Carlos E. R. wrote:
Yes, but /boot is where the space issue is. On the last kernel
update, I had to free up space to let it install. Just remove the rpms. You have entries in grub that will crash.
I removed the old kernels from the boot menu.
Ah, manually. If you just use rpm --erase, all that is done for you. Notice that grub2 might recreate those entries you deleted. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG3MwUACgkQIvFNjefEBxrZmwCfb0Fxh9mPRvW1tCW423A71O8e IqQAnRgfYvi0ovs4y9GiS59R+qDYoSkv =Bicj -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
Ah, manually. If you just use rpm --erase, all that is done for you. Notice that grub2 might recreate those entries you deleted.
I have done that. BTW, I've noticed some repeat messages on this list. This is the 2nd time I've seen this one and one of my posts appeared 3 times. Server problems? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
Carlos E. R. wrote:
Ah, manually. If you just use rpm --erase, all that is done for you. Notice that grub2 might recreate those entries you deleted.
I have done that.
BTW, I've noticed some repeat messages on this list. This is the 2nd time I've seen this one and one of my posts appeared 3 times. Server problems?
No repeated messages here, but the distribution does seem a bit slow. -- Per Jessen, Zürich (18.5°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-06-11 16:53, James Knott wrote:
Carlos E. R. wrote:
Ah, manually. If you just use rpm --erase, all that is done for you. Notice that grub2 might recreate those entries you deleted.
I have done that.
BTW, I've noticed some repeat messages on this list. This is the 2nd time I've seen this one and one of my posts appeared 3 times. Server problems?
Nope, I see no repeats. And no delays in your email, either: Date: Tue, 11 Jun 2013 10:53:07 -0400 Received: from IMPmx8.adm.correo (10.20.102.115) by tems9.backend.correo (8.5.137.03) id 51102A7C02007D32 for robin.listas...; Tue, 11 Jun 2013 16:53:24 +0200 Less than 20 seconds end to end. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlG3PFcACgkQIvFNjefEBxqNkgCfXGK0GjRadjglUNmWyERMdMpL hywAoNzzyOr5Dv3g7uLXr44POMLF5JzK =MJ3U -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Peter
I've just run into the problem of my /boot partition filling up due to multiple kernel versions, but I don't understand how to resolve it.
[...] If the multiversion provision does not work for you or suit your use case, remove unwanted/unused kernels with zypper: zypper -v rm `rpm -qa *kernel* |grep 3\.9\.3\-9` but use the kernel version number you wish removed. I removed 3.9.3-9 because it only existed a few days and I didn't feel comfortable that it was solid. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
Carlos E. R. -
ellanios82 -
James Knott -
Linda Walsh -
Marcus Meissner -
Patrick Shanahan -
Per Jessen -
Peter