search for: lvm1

...ode providing iscsi disk, the disks is mounted on two linux kvm host and one backup server. The iscsi disk has lvm on it, the logical volume groups are visible on all servers. On the backup server I have the following running: # guestmount --version guestmount 1.40.2 # guestmount --ro -a /dev/lvm1-vol/sr8-disk1a -a /dev/lvm1-vol/sr8-disk2 -a /dev/lvm1-vol/sr8-disk3 -a /dev/lvm1-vol/sr8-disk4 -a /dev/lvm1-vol/sr8-disk5 -a /dev/lvm1-vol/sr8-disk6 -m /dev/sdb2 /mnt/sr8-sdb2 # rsync --archive --delete --partial --progress --recursive --no-links --no-devices --quiet /mnt/sr8-sdb2/ /srv/stor...

...e crash (it was clunking before it definitely died!). It was running on SuSE 9.0 before. I just finished to install a fresh copy of CentOS 4.4 on a new hard disk. I want to know if it's possible to "import" the old LVM array into the fresh CentOS install. We have 1 volume group (LVM1) that contains 3 whole hard drives. I had the time to save some informations before the system hard drive crashed definitely: I have vgcfgrestore info, i have volgroups_001.conf, i have the full /etc directory and pvdata. Here is a part of the info i have: PVDATA: ======= --- Physical volume -...

hi, My volume group is vg. Inside that i have around 10 lvm partitions (each of 100GB). When I try to remove partitions using lvremove /dev/vg/lvm1 It acts like the machine freezes and after a long time the lvremove process gets killed saying "Killed" Whats wrong here. I don't see anything interesting in /var/log/message Thanks Paras.

...idth="100%" align=center> Recently I update a server running CentOS 4.3 to kernel 2.6.9-42.0.2. After the update it had a problem to mount LVM partitions, showing the follow error during boot: No volume groups found Activating logical volumes Unable to find volume group "lvm1" ERROR: /bin/lvm exited abnormally! (pid 199) Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill...

Has anybody encountered this problem? I have a box that has FC2 installed. I wanted to trash the FC2 installation and install CentOS 4. I have a pxeboot/dhcp/kickstart environment and so I tried automatic disk partitioning (clear all partitions and then create new ones), manual disk partitioning but everything else is automated and finally, zero automation, just a manual installation through

Recently I update a server running CentOS 4.3 to kernel 2.6.9-42.0.2. After the update it had a problem to mount LVM partitions, showing the follow error during boot: No volume groups found Activating logical volumes Unable to find volume group "lvm1" ERROR: /bin/lvm exited abnormally! (pid 199) Creating root device Mounting root filesystem mount: error 6 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill...

...VM expert, it seems that ext2online does what you want. My CentOS4 box here has ext2online included; I have not had a chance to try it out, so I can't comment on how well it works. However, what I have read is that the LVM2 metadata format is more robust and removes many of the limitations of LVM1. In trying to check on this, I looked for specific information on how this was the case, but have not been able to at this point. The ext2/3 filesystem wasn't designed for resizing online, so it's quite nice one can do it at all; but it appears the LVM2 approach is to rely on the e2fsprog...

Just discovered that on CentOS 4.1 when you issue the command: lvcreate -s -n temp -L2G /dev/vgname/lvname to create a snapshot, you get the error message: snapshot: Required device-mapper target(s) not detected in your kernel I've checked and recheck my spelling and tried using the device created under /dev/mapper. I've tried it on both x86_64 and on i386. Works as expected under

...;' else: arch_libdir = ''lib'' kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' memory = 2048 vcpus=4 shadow_memory = 8 name = "communicator" vif = [ ''bridge=eth0'' ] acpi = 1 apic = 1 disk = [ ''phy:/dev/lvm1/communicator,hda,w'', ''phy:/dev/cdrom,hdc:cdrom,r'' ] vfb = [ ''type=vnc,vncdisplay=10'' ] device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' boot="dc" monitor=1 sdl=1 vnc=0 serial=''...