similar to: LVM question during an upgrade

Once upon a time, m.roth at 5-cent.us <m.roth at 5-cent.us> said: > Here's a question: all of the arguments you're giving have to do with VMs. > Do you have some for straight-on-the-server, non-VM cases? I've used LVM on servers with hot-swap drives to migrate to new storage without downtime a number of times. Add new drives to the system, configure RAID (software or

On 06/23/2015 08:10 PM, Marko Vojinovic wrote: > Ok, you made me curious. Just how dramatic can it be? From where I'm > sitting, a read/write to a disk takes the amount of time it takes, the > hardware has a certain physical speed, regardless of the presence of > LVM. What am I missing? Well, there's best and worst case scenarios. Best case for file-backed VMs is

Hi all, We are hitting an error in the centos 7 installation with our kickstart configuration. =============================================================================== An unknown error has occurred =============================================================================== anaconda 21.48.22.56-1 exception report Traceback (most recent call first): File

On 6/24/2015 1:06 PM, m.roth at 5-cent.us wrote: > Gordon Messmer wrote: >> On 06/23/2015 08:10 PM, Marko Vojinovic wrote: >>> Ok, you made me curious. Just how dramatic can it be? From where I'm >>> sitting, a read/write to a disk takes the amount of time it takes, the >>> hardware has a certain physical speed, regardless of the presence of >>>

On Tue, 23 Jun 2015 14:23:52 -0400 Mauricio Tavares <raubvogel at gmail.com> wrote: > On Tue, Jun 23, 2015 at 1:54 PM, Marko Vojinovic <vvmarko at gmail.com> > wrote: > > On Tue, 23 Jun 2015 11:15:30 -0500 > > Jason Warr <jason at warr.net> wrote: > >> > >> I'm curious what has made some people hate LVM so much. > > > > (3)

Robert Heller wrote: > At Thu, 25 Jun 2015 11:03:18 -0400 CentOS mailing list <centos at centos.org> > wrote: >> On Wed, June 24, 2015 16:11, Chuck Campbell wrote: >> > >> > Is there an easy to follow "howto" for normal LVM administration >> > tasks. I get tired of googling every-time I have to do something >> > I don't remember

Hi to all, i am facing a really strange problem ,and i am not able to find a solution by myself and it is really critical for me to solve it asap :( I have replaced old sata disk with new one on centos , i did a whole cp -a copy from single mode do new disk. What i have done? 1) using fdisk created sdb1 (Linux) and sdb2 (Linux LVM) 1) created volume group boss on new disk at sda2 2) created

My gut feeling is that this is related to a RAID1 issue I'm seeing with 7.6. See email thread "CentOS 7.6: Software RAID1 fails the only meaningful test" I suggest trying to boot from an earlier kernel. Good luck! Ben S On Wednesday, December 5, 2018 9:27:22 AM PST Gordon Messmer wrote: > I've started updating systems to CentOS 7.6, and so far I have one failure. >

> I've started updating systems to CentOS 7.6, and so far I have one > failure. > > This system has two peculiarities which might have triggered the > problem. The first is that one of the software RAID arrays on this > system is degraded. While troubleshooting the problem, I saw similar > error messages mentioned in bug reports indicating that sGNU/Linux > ystems

Dear, I have a lot of problems with LVM of CentOS when upgrading to the new kernel 2.6.18. When I have compiled the new kernel and I insert the new rules in the GRUB configuration and when I restart the server I get the warnings that the group volume ?VolGroup00? not found and then the kernel has a panic situation (Kernal panic - not syncing: Attempting to kill init!). This problem I have on

I'm trying to work out the kinks of a proprietary, old, and clunky application that runs on CentOS. One of its main problems is that it writes image sequences extremely non-linearly and in several passes, using many CPUs, so the sequences get very fragmented. The obvious solution to this seems to be to use SSDs for its output, and some scripts that will pick up and copy our the sequences

I have an 8-core SuperMicro Xeon server with CentOS 6.3. The OS is installed on a 120 GB SSD connected by SATA, the machine also contains an Areca SAS controller with 24 drives connected. The motherboard is a SuperMicro X9DA7. When I installed the OS, I used the default options, which creates an LVM volume group to contain / and /home, and keeps /boot and /boot/efi outside the volume group.

On Wed, 5 Dec 2018 at 14:27, Benjamin Smith <lists at benjamindsmith.com> wrote: > > My gut feeling is that this is related to a RAID1 issue I'm seeing with 7.6. > See email thread "CentOS 7.6: Software RAID1 fails the only meaningful test" > You might want to point out which list you posted it on since it doesn't seem to be this one. > I suggest trying to

I finally got 5.1 to boot after install (install couldn't keep the disk IDs from getting crossed up, so at reboot partitions were not where install said they would be). I needed to compile vmware and nvidia modules, but decided to upgrade first. Told yumex to upgrade everything. When I went to reboot the VG with / on it is not seen by the kernel. (root partition is LVM on top of RAID

On 12/5/18 9:27 AM, Gordon Messmer wrote: > The content of /var/log/messages is here: > ????https://paste.fedoraproject.org/paste/n-E6X76FWIKzIvzPOw97uw I don't have much new information, other than that I tested booting a similar system with an intentionally degraded RAID volume. That one booted properly, so I don't think that was the problem. The dm-cache device still needs

On Fri, Feb 27, 2015 at 9:44 PM, John R Pierce <pierce at hogranch.com> wrote: > On 2/27/2015 8:00 PM, Marko Vojinovic wrote: >> >> And this is why I don't like LVM to begin with. If one of the drives >> dies, you're screwed not only for the data on that drive, but even for >> data on remaining healthy drives. > > > with classic LVM, you were

Hi there. I'm trying to use thin provisionned LVM for som eguests, and I'm having a problem. Until now, I use LVM pool with success. Here's my pool definition: <pool type='logical'> <name>data</name> <uuid>7f18e030-9d2d-805e-c65f-d12d0681b0a9</uuid> <capacity unit='bytes'>0</capacity> <allocation

Hello Gentlemen, I would like to ask a question about an issue I have with the Centos 6.3 installation. I have installed a Centos 6.3 on a server we used before with 5.4 on Friday. I have created a KS file to let me connect to the server via VNC and have all repos and packages preconfigured. I only needed to partition the hard drive using VNC. During the partition process I selected which

I've started updating systems to CentOS 7.6, and so far I have one failure. This system has two peculiarities which might have triggered the problem. The first is that one of the software RAID arrays on this system is degraded. While troubleshooting the problem, I saw similar error messages mentioned in bug reports indicating that sGNU/Linux ystems would not boot with degraded software

After upgrading the kernel package, my Centos 7 server didn't boot. Here is a small summary: old kernel = kernel-3.10.0-123.4.4.el7.x86_64 (everything just fine) new kernel = kernel-3.10.0-123.6.3.el7.x86_64 root partition is on a primary partition, NOT on a LVM volume /var partition is on a LVM volume new kernel's boot problem = systemd cannot mount /var partition saying requirements