similar to: hacking grub to control number of retained kernels.

On Fri, Sep 02, 2016 at 10:52:05PM -0400, Fred Smith wrote: > I've recently had this problem on two C7 systems, wherein when doing "yum > update", I get a warning about /boot being low on space. > > both systems were installed using the partition size recommended by > Anaconda, right now "df -h" shows /boot as 494M, with 79M free. > > I don't

I have 4 kernels in /boot, leaving on 20MB which is not enough for the next one. I had installonly_limit= set at 5, as there were some kernel problems.? After I got the error that there was not enough room for another kernel, I set installonly_limit= to 3 and did the update with --exclude=kernel* That worked to update everything else, but not remove the oldest kernel. How can I remove the

First off - let me say I am not an administrator.?? I need to know?if there is an easy way to increase my /boot partition.? When I installed CentOS 6 after running 5, it was my oversight not to increase the /boot size.? it's too small and I can't do yum updates. if it's not easy to actually increase it, is it safe to take a chunk in my root filesystem (like /new.boot or something) and

On 1/8/19 5:30 PM, mark wrote: > Robert Moskowitz wrote: >> I have 4 kernels in /boot, leaving on 20MB which is not enough for the >> next one. >> >> I had installonly_limit= set at 5, as there were some kernel problems. >> After I got the error that there was not enough room for another kernel, >> I set installonly_limit= to 3 and did the update with

>> What size is recommended for the /boot partition? After doing a fresh >> install and lengthy backup restore I realized I only made it 200M. Is >> this going to be a problem? > > Mine was about 500 MB and I removed some kernels because I got a warning the > partition was getting full. > > With only two kernels installed, 182 MB are used. I would suggest 1 GB

In order to keep only 3 kernel images on a CentOS 7 I edited /etc/yum.conf and I put installonly_limit=3 This parameter works for standard kernel images, but does not work for rescue images: $ ls -al /boot/vmlinuz* -rwxr-xr-x 1 root root 5027376 May 13 20:46 /boot/vmlinuz-0-rescue-2554e2ffad84452bb07401bed0a61089 -rwxr-xr-x 1 root root 3084288 Jun 27 06:42

Nicolas Thierry-Mieg wrote on 24/08/2015 00:24: >> installonly_limit=3 >> >> >> This parameter works for standard kernel images, but does not work for >> rescue images: >> > <snip> >> Is there a way to keep rescue images within a certain limit? > > man yum.conf , search for installonlypkgs (that's on centos6, might vary in 7)

Default boot volume on Fedora is 500M, with a kernel installonly_limit of 3. So far this seems sufficient, even accounting for the "rescue kernel" (which is really a nohostonly initramfs, which is quite a bit larger than the standard hostonly initramfs used for numbered kernels).

Hi, Such a simple problem, but I can't figure out the cause. Supermicro server with a Xeon E3-1200 cpu. 1U entry level item. Using CentOS 7 from ~$root --- systemctl reboot Server disconnects my ssh connection and never comes back up. Go to the server and the power is on but the server is not accessible by ssh. When I connect a monitor and keyboard --- non-responsive. It's like

I have a CentOS 6 machine that was initially installed as CentOS 6.4 in May of 2013. It's /boot filesystem is 200M which, IIRC, was the default /boot size at the time. The most recent kernel update (2.6.32-573.18.1.el6) fails because of lack of space in /boot. The workaround is edit /etc/yum.conf, reduce installonly_limit from 5 to something lower (I used 3), remove the oldest kernel via

What do you mean? Wouldn't the kernel version always be the actual running version of the kernel that was booted? Ben On 3/26/19 6:16 PM, wuzhouhui wrote: >> -----Original Messages----- >> From: "Benjamin Hauger" <hauger at noao.edu> >> Sent Time: 2019-03-27 00:15:21 (Wednesday) >> To: centos at centos.org >> Cc: >> Subject: Re: [CentOS]

kdump operates by booting a fresh kernel to capture the context of a crashed kernel, and so the only way for kdump to dump a kernel is to crash it and cause kdump to invoke its post-crash kernel. You can manually force a running kernel to panic (and invoke a correctly-configured kdump) with the following command sequence: > echo 1 > /proc/sys/kernel/sysrq > echo c >

Howdy, Running a round of updates from 6.3 to 6.4 and I'm seeing the following on all the servers. Want to make sure I'm not going to end up with a kernel panic if I reboot into the new kernel or have any other issues. Apr 22 11:10:21 www kdump: kexec: unloaded kdump kernel Apr 22 11:10:21 www kdump: stopped Apr 22 11:10:21 www kdump: mkdumprd: failed to make kdump initrd Apr 22

Hi, This set of patches contains initial kexec/kdump implementation for Xen v2 (previous version were posted to few people by mistake; sorry for that). Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code.

Hi, This set of patches contains initial kexec/kdump implementation for Xen v2 (previous version were posted to few people by mistake; sorry for that). Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code.

Hi, This set of patches contains initial kexec/kdump implementation for Xen v2 (previous version were posted to few people by mistake; sorry for that). Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code.

Hi, I have a specific needs that requires yum do not to uninstall old version when install new one. For example, I found that yum install kernel will install new kernel, and old kernel will remained. But yum install <something-else> will uninstall old version after install new one, how to disable it? Thanks.

Hello, I am new in this mailing,please if somebody knows how to make kdump able to load in startup. i will be very thankful, -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20090409/d3435a68/attachment-0002.html>

Hello, I've used pungi with the following configuration: repo --name=centos-base --baseurl=ftp://mirrors/centos/6/os/x86_64 --cost=1 -- excludepkgs=qemu-kvm repo --name=centos-updates --baseurl=ftp://mirrors/centos/6/updates/x86_64 -- cost=1 --excludepkgs=qemu-kvm repo --name=xen4centos -- baseurl=http://mirror.centos.org/centos/6/xen4/x86_64/ --cost=1 %packages @base @core

Hey All, I just assembled a new machine. Mother Board: Gigabyte 78LMT-USB3 Processor: AMD FX8350 Memory: Corsair CMZ16GX3M2A1600C10 2x8 GB Video: BFG Tech Nvidia GeForce 9600 GT I tried the 6.6 x86_64 netinstall disk. I tried the 6.6 x86_64 install DVD Both fail at the same place: Anaconda installer init version 13.21.229 starting mounting /proc filesystem... done creating /dev