similar to: heads up: /boot space on kernel upgrade

On Sat, February 13, 2016 5:57 am, Timothy Murphy wrote: > Devin Reade wrote: > >> 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. > > As a matter of interest, is there any advantage today > in having a /boot partition? > I thought

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).

Devin Reade wrote: > 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

On Sat, February 13, 2016 2:24 pm, David Both wrote: > +1 Valeri. I agree that things have changed a lot! _things_ changed? I wouldn't quite agree. It is people who have changed definitely. As far as things are concerned, they have changed a lot, but not fundamentally. Disks are huge, but they still are not infinite. Number of inodes filesystem can have increased multiple orders of

On Wed, Nov 18, 2015 at 09:49:43PM -0700, Devin Reade wrote: > --On Wednesday, November 18, 2015 11:07:12 PM -0500 Fred Smith > <fredex at fcshome.stoneham.ma.us> wrote: > > >But it isn't at all obvious how one would do a new RAID1 setup in > >Anaconda > > Don't feel bad. The abortion that is the RHEL/CentOS 7 graphical > install interface is far too

+1 Valeri. I agree that things have changed a lot! However, Devin, the answer to your question is that the /boot partition is a necessity in a LVM environment, which everything else is by default. The /boot partition cannot be a logical volume; it must be a raw disk partition with an EXT[34] file system. On 02/13/2016 03:19 PM, Valeri Galtsev wrote: > On Sat, February 13, 2016 5:57 am,

On Nov 18, 2015, at 9:49 PM, Devin Reade <gdr at gno.org> wrote: > > The one thing I would point out regarding the above link is that despite > conventional UNIX wisdom, *don't* put /usr on a separate filesystem > in CentOS 7. <sarcasm>Thank you RedHat</sarcasm> > > Flames to /dev/null. Sorry, you don?t get to throw that grenade and then run away. The

>> 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

Devin Reade wrote: > 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. As a matter of interest, is there any advantage today in having a /boot partition? I thought it went back to the days when the boot-loader had to be near the beginning of the disk? --

I've got a fresh CentOS 7 test machine, fully patched. The command: shutdown -h now surprisingly does not halt the machine. Instead it reboots it. WTF? I found the following Debian discussion which seems to be the same issue: <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766338> However, removing kexec-tools in this case did not solve the problem. Nor does

Now don't go bugging people asking when CentOS 6.7 will be out. "When it's ready." In upgrading from RHEL 6.6 to 6.7, I did find that I had to disable my 3rd party repos (elrepo and epel) in order to avoid yum erroring out. Plus I did the usual "yum clean all". (I don't use the PackageKit GUI as it's been unable to complete for quite a few months without

I noticed that (in a case with a two disk md mirror and lvm), the CentOS 7 installer is now placing /boot as the *last* partition on the disk. I'm assuming that others are seeing this behavior. Does anyone know why it's now the last instead of the first? (Seems to work, though.) Devin

Saturday I did an upgrade from 5.3 (original install) to 5.4. Saturday night, /etc/cron.weekly reported the following: /etc/cron.weekly/99-raid-check: WARNING: mismatch_cnt is not 0 on /dev/md0 md0 holds /boot and resides, mirrored, on sda1 and sdb1. md1 holds an LVM volume containing the remaining filesytems, including swap. The underlying hardware is just a few months hold,

While attempting to debug something else I ran across this: ssh -vvv somehost . . . debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/identity-cert type -1 debug3: Not a RSA1 key file /root/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing

Hi all! I'm still on C6. I'm using a RAID1 configuration (Linux software RAID) and I'd like to either use the same one, or possibly configure it on new drives (larger) when I upgrade to C7. (I'm really feeling the need to move off C6.) But it isn't at all obvious how one would do a new RAID1 setup in Anaconda, and I don't find any user reports or other info on this in the

Does anyone have the magic incantation required to getting *independent* multi-monitors going under CentOS 7? Ideally under xfce or trinity, but I'm interested about GNOME/KDE observations as well. I'm trying to move my main workstation from CentOS5 to CentOS7 and while the spanned desktop works, not having independent monitors really cuts into my productivity. i.e.: I couldn't

It looks like someone pooched a domain transfer, and the whois entry for centos.org is missing its NS records. I've sent an email to the whois tech contact @redhat, but I'm sending this to the list to hopefully bring it to someone else's attention, as well. Hopefully it gets gets out before my mailserver expires its DNS cache for centos.org. Expect centos.org to be offline for a bit

On Sat, February 13, 2016 2:50 pm, John R Pierce wrote: > On 2/13/2016 12:19 PM, Valeri Galtsev wrote: >> It is interesting to observe how perceptions are changing over time. >> Decade or two ago we were partitioning small then drives (thus loosing >> some of the space) just to separate regular users from those places >> vital >> for secure and reliable running of

Ok, trying to bypass the usual flames (I used CDE for years, then KDE until it got dumbed-down too much, and we all know how GNOME has turned out) ... I've decided to try out xfce on CentOS 7. I grabbed xfce from epel by installing the following via yum: epel-release @xfce So far it's pretty good, and is giving me the basic features I'm looking at without getting in my way.

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