search for: logvol01

...u.lst # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/mapper/vg_xen-LogVol01 # initrd /initrd-[generic-]version.img #boot=/dev/sdb default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.32.57-2.el6xen.x86_64) root (hd0,0) kernel /xen.gz dom0_mem=1024M cpufreq=xen dom0_max_vcpus=1 dom0_vcpus_pin kernel /vmlinuz-2.6.32.57-2.el6xen.x86_64 ro ro...

Dear All, Previously we have used CentOS4.4 release with Supported Cluster Suite and DRBD 8.0.0 Active/passive (failover) We have build the DRBD 8.0.0 Source in CentOS4.4 Setup We have configured the DRBD Resource with default OS installed LVM (/dev/mapper/vgroot-LogVol00 and /dev/mapper/vgroot-LogVol01) Partition and its working fine Partition Tables are listed below ================================= Filesystem Size Used Avail Use% Mounted on /dev/mapper/vgroot-LogVol02 3.0G 1.1G 1.7G 39% / /dev/mapper/vgroot-LogVol03 11G 8.5G 1.7G...

...nv->open: No space left on device error: cannot open Packages index using db3 - No space left on device (28) error: cannot open Packages database in /var/lib/rpm Traceback (most recent call last): <...> # df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol01 5.0G 3.6G 1.2G 76% /var /dev/mapper/VolGroup00-LogVol04 1008M 456M 501M 48% /var/log /dev/mapper/VolGroup00-web 4.9G 140M 4.5G 3% /var/www # mount /dev/mapper/VolGroup00-LogVol01 on /var type ext3 (rw) /dev/mapper/VolGroup00-LogVol04 on /var/log type ext3 (rw) /dev/mapper/VolGrou...

Hello, I have a server running CentOS 4.7 and I want to add a new USB-HD for backup some data. I made the file system as ext3 with the command: / mkfs -t ext3 /dev/sdb1/ After that I did add a new Volume Group and Logical Volume (/VolGrup01-LogVol01) /on that file system and mounted it as /backup. It worked fine but when I did reboot the server It wont mount /backup and I got the following error even after the system boots and I try to mount it manually: /mount: special device /dev/VolGrup01/LogVol01 does not exist/ I will appreciate any...

...rnel. Please check the grub.conf. [/QUOTE] Looking at grub.conf, I see the following: #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-128.1.10.el5xen) root (hd0,0) kernel /xen.gz-2.6.18-128.1.10.el5 ro root=/dev/VolGroup00/LogVol01 ide0=noprobe ide1=noprobe initrd /initrd-2.6.18-128.1.10.el5.img title CentOS (2.6.18-128.1.10.el5) root (hd0,0) kernel /vmlinuz-2.6.18-128.1.10.el5 ro root=/dev/VolGroup00/LogVol01 ide0=noprobe ide1=noprobe initrd /initrd-2.6.18-128.1.10.el5.img title CentOS (2.6.18...

...edure with partitions on LVM does NOT result in a booting system! -) When booting from the newly imaged drive, it starts the boot just fine but quits at: ---------------------------- Activating logical volumes Volume group "VolGroup00" not found Trying to resume from /dev/VolGroup00/LogVol01 Unable to access resume device (/dev/VolGroup00/LogVol01) Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' --SNIP-- switchroot: mount failed: no such file or directory Kernel panic - not syncing: Attempted to kill init! ---------------------------...

...and I've run into an issue that I can't find a good answer to in the docs. I have the following RAID setup: md0: sda1 and sdb1, RAID 1. This is /boot md1: sda2 and sdb2, RAID 1. This is a PV for LVM. VolGroup00, this is the volume group and md1 is the only PV in it. LogVol00 is swap LogVol01 is / LogVol02 is /home So, I tested to see what happens if I disable sdb in virtualbox. Machine booted find and I was able to see that part of the raid array was gone. I reattached the disk and rebuilt the array mdam --add /dev/md0 /dev/sdb1 mdam --add /dev/md1 /dev/sdb2 The array rebuilt withou...

...rnel. Please check the grub.conf. [/QUOTE] Looking at grub.conf, I see the following: #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-128.1.10.el5xen) root (hd0,0) kernel /xen.gz-2.6.18-128.1.10.el5 ro root=/dev/VolGroup00/LogVol01 ide0=noprobe ide1=noprobe initrd /initrd-2.6.18-128.1.10.el5.img title CentOS (2.6.18-128.1.10.el5) root (hd0,0) kernel /vmlinuz-2.6.18-128.1.10.el5 ro root=/dev/VolGroup00/LogVol01 ide0=noprobe ide1=noprobe initrd /initrd-2.6.18-128.1.10.el5.img title CentOS (2.6.18...

.../boot tmpfs 1014 0 1014 0% /dev/shm /dev/mapper/VolGroup00-LogVol05 48481 6685 39295 15% /home /dev/mapper/VolGroup00-LogVol03 961 18 894 2% /tmp /dev/mapper/VolGroup00-LogVol01 7781 2051 5329 28% /usr /dev/mapper/VolGroup00-LogVol02 5239 327 4642 7% /var $ sudo lvm lvreduce -L -1000M /dev/VolGroup00/LogVol05 Rounding up size to full physical extent 992.00 MB WARNING: Reduci...

...I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xdbdbdbdb Device Boot Start End Blocks Id System /dev/sdb1 * 1 13 104391 83 Linux /dev/sdb2 14 9730 78051802+ 8e Linux LVM Disk /dev/mapper/VolGroup00-LogVol01: 2080 MB, 2080374784 bytes 255 heads, 63 sectors/track, 252 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x30307800 Disk /dev/mapper/VolGroup00-LogVol01 doesn'...

...ut when I try to use both drives and mirror the partitions, I start having problems. Anaconda crashes as it is trying to format the drives. This is what I'm trying to create: /dev/md0: 200MB, /boot /dev/md1: 2GB, swap /dev/md2: rest of the drive, LVM PV LogVol00: 10GB, / LogVol01: rest of the VG, /home I uploaded the anaconda log to the CentOS bugtracker, but I don't know if or when I should expect a response from that, so I'm asking here as well. If you want to see the log, here's the link: http://bugs.centos.org/view.php?id=2652 Is there a way I can work ar...

...ted by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol01 # initrd /initrd-version.img #boot=/dev/sda default=3 timeout=10 #0 title Red Hat Enterprise Linux Server (2.6.18-8.el5-smp) root (hd0,0) kernel /vmlinuz-2.6.18-8.el5 ro root=/dev/VolGroup00/LogVol01 crashkernel=128M@16M initrd /initrd-2.6.18-8.el5.img #1 title R...

...ted. The following diagram shows how dm-ioband is applied to the existing logical volumes. run "service ioband start" ===> ------------------------------- ------------------------------- | LogVol00 | LogVol01 | | LogVol00 | LogVol01 | | (dm-linear) | (dm-linear) | | (dm-ioband) | (dm-ioband) | |-------------------------------| |-------------------------------| | VolGroup00 | | LogVol00-orig | LogVol01-orig | --------------------------...

...ted. The following diagram shows how dm-ioband is applied to the existing logical volumes. run "service ioband start" ===> ------------------------------- ------------------------------- | LogVol00 | LogVol01 | | LogVol00 | LogVol01 | | (dm-linear) | (dm-linear) | | (dm-ioband) | (dm-ioband) | |-------------------------------| |-------------------------------| | VolGroup00 | | LogVol00-orig | LogVol01-orig | --------------------------...

...ted. The following diagram shows how dm-ioband is applied to the existing logical volumes. run "service ioband start" ===> ------------------------------- ------------------------------- | LogVol00 | LogVol01 | | LogVol00 | LogVol01 | | (dm-linear) | (dm-linear) | | (dm-ioband) | (dm-ioband) | |-------------------------------| |-------------------------------| | VolGroup00 | | LogVol00-orig | LogVol01-orig | --------------------------...

...tallation. However, I want to leave one of the existing partitions (/scratch) untouched during the installation. Here is my current layout (LogVol00 is swap so not shown in the df output below): # df -hl Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol01 36G 11G 24G 30% / /dev/sda1 99M 17M 78M 18% /boot /dev/mapper/VolGroup00-LogVol02 36G 9.7G 24G 29% /scratch # vgscan Reading all physical volumes. This may take a while... Found volume group "Vol...

.../boot_ The second partition, /dev/sda2 is the one I really want and it is an lvm partition. When I am booted from this drive (as the installed IDE drive, not as a usb drive) has for its /etc/fstab: # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol01 / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 /dev/VolGroup00/Log...

I posted this to the Fedora-list, but thought I might get some additional information here as well. I have a HD that refuses to mount with a 'bad magic number in super-block'. I'm running FedoraCore 6 x86_64. [root at moe ~]# fdisk -l /dev/hdc Disk /dev/hdc: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes

...st. It used to run but I added another logical volume to the disk line for additional disk space and it now crashes. Here''s the difference between the good and bad files: diff newcentos44 centos44 5c5 < disk = [ ''phy:/dev/hda2,sdb1,w'',''phy:/dev/VolGroup08/LogVol01,sdb2,w'',''phy:/dev/VolGroup08/LogVol02,sdb3,w'',''phy:/dev/VolGroup09/VarRoot,sdb4,w''] --- > disk = [ ''phy:/dev/hda2,sdb1,w'',''phy:/dev/VolGroup08/LogVol01,sdb2,w'',''phy:/dev/VolGroup08/LogVol02,sdb3,w'...

Alle, I'm trying to setup diskdump on a FJ E7110 notebook. Disk partitions were auto configured, using /dev/hda1 for /boot and /dev/hda2 for VolGroup00 (LogVol00 (/) and LogVol01 (swap)). Can diskdump be configured to use the logical swap volume? When I try to do the setup, the following occurs: [root at HOST sysconfig]# service diskdump initialformat Formatting dump device: /dev/VolGroup00/LogVol01: skipped (swap device) [root at HOST sysconfig]# Any help would be app...