search for: volgroup

Hey, Can anyone tell me why option 1 works and option 2 fails ? I know I need swap and such, however in trouble shooting this issue I trimmed down my config. It fails on trying to format my logical volume, because the mount point does not exist (/dev/volgroup/logvol) It seems that with option 2, the partitions are created and LVM is setup correctly. However the volgroup / logvolume was not made active, so my /dev/volgroup/logvol did not exist. Running `lvm lvchange -a -y pathname` from with in the shell after anaconda failed made the volgroup / log...

Thanks all for the advice. It seems there is an issue with Dracut booting from these hosts when LVM is used. dracut: Scanning devices sda2 for LVM logical volumes VolGroup/lv_swap VolGroup/lv_root dracut: inactive '/dev/VolGroup/lv_swap' [1.94 GiB] inherit dracut: inactive '/dev/VolGroup/lv_root' [230.69 GiB] inherit dracut: PARTIAL MODE. Incomplete logical volumes will be processed. dracut: Operation prohibited while global/metadata_read_only is set...

...wn node 'vm_ipa-data_rimage_0'. grub2-probe: error: ../grub-core/kern/disk.c:236:disk `lvmid/uhx5FA-RmdV-cPYP-ELEA-pUrn-FfHl-M2RBEV/JQKCwn-RhKX-ek4u-VJxX-ja9j-rtAD-fVUBGc' not found. "vgdisplay --verbose" output includes: ? --- Volume group --- ? VG Name?????????????? VolGroup ? System ID ? Format??????????????? lvm2 ? Metadata Areas??????? 2 ? Metadata Sequence No? 2053 ? VG Access???????????? read/write ? VG Status???????????? resizable ? MAX LV??????????????? 0 ? Cur LV??????????????? 82 ? Open LV?????????????? 18 ? Max PV??????????????? 0 ? Cur PV?????????...

I've install a CentOS Stream 9 system from a kickstart file that specified (among other things) several logical volumes: logvol / --fstype="ext4" --size=10240 --name=lv_root --vgname=VolGroup logvol /var --fstype="ext4" --size=4096 --name=lv_var --vgname=VolGroup logvol swap --fstype="swap" --size=2048 --name=lv_swap --vgname=VolGroup When that system rebooted, the kernel args did specify "rd.lvm.lv=VolGroup/lv_root rd.lvm.lv=VolGroup/lv_swap", but did no...

...order to also add dm-integrity data to some LVs.? I've added new PVs to my VG, and I've converted some of my LVs to raid1 types, but I also have one thin pool that I use for VMs with multiple layers of snapshots.? That pool can't be converted, directly: # lvconvert --type raid1 -m 1 VolGroup/vm_pool --yes ? Operation not permitted on LV VolGroup/vm_pool type thinpool. Is it sufficient to simply convert the tdata and tmeta LVs to raid1 type?? Should I also convert lvol0_pmspare?? Is there anything else I should consider? # lvs VolGroup/vm_pool VolGroup/vm_pool_tmeta VolGroup/vm_poo...

...I'm trying out kickstart at all, so I rather think I'm doing something wrong in the kickstart configuration than it is a Xen issue. I use a modified kickstart file from an earlier manual installation with a very basic filesystem setup. It fails with "SystemError: vgcreate failed for VolGroup00". The Xen VM file is allowed to grow up to 2GB. The kickstart commands for partioning are: clearpart --all --initlabel --drives=xvda part /boot --fstype ext3 --size=100 --ondisk=xvda part pv.2 --size=0 --grow --ondisk=xvda volgroup VolGroup00 pv.2 --pesize=32768 pv.2 logvol / --fstype ext3...

...Messmer wrote: > 1: The system also includes a volume group named "BackupGroup" and > that group activates on boot (post-dracut).? Why are those LVs > activated when rd.lvm.lv is specified? As far as I can tell, this is because in the dracut boot process, the device backing VolGroup is activated, but the device backing BackupGroup is not.? As a result, the latter device triggers a udev event after the normal root FS is mounted, and udev creates a transient systemd unit to start the BackupGroup VG.? No udev event for VolGroup == no furter activation. > 2: Why didn'...

Hi, I'm trying to setup the provisioning of new OpenStack hypervisors with cinder volumes on them. The problem is that kickstart doesn't allow dashed in volume group names? I tried this: volgroup cinder-volumes --pesize=4096 pv.02 and this: volgroup cinder--volumes --pesize=4096 pv.02 but in both cases I end up with a volume group named "cindervolumes" on the system. Any idea what I have to do to accomplish this? Defining VGs with dashes works perfectly fine on the command lin...

...Subject: Re: [Xen-users] my bootlog To: "Boris Derzhavets" <bderzhavets@yahoo.com> Date: Saturday, 22 August, 2009, 11:12 AM Please check what wrong here grub.conf        title Fedora (2.6.30-rc6-tip)         root (hd0,6)         kernel /vmlinuz-2.6.30-rc6-tip ro root=/dev/mapper/VolGroup-lv_root rhgb quiet         initrd /initrd-2.6.30-rc6-tip.img title Xen 3.4 / Fedora kernel 2.6.30-rc6-tip         kernel /boot/xen-3.4.gz         module /boot/vmlinuz-2.6.30-rc6-tip root=/dev/mapper/VolGroup-lv_root ro console=tty0         module /boot/initrd-2.6.30-rc6-tip.img [root@localhost boo...

On Thu, Dec 4, 2014 at 12:39 PM, Bob Ball <bob.ball at citrix.com> wrote: > Thanks all for the advice. > > It seems there is an issue with Dracut booting from these hosts when LVM is used. > > dracut: Scanning devices sda2 for LVM logical volumes VolGroup/lv_swap VolGroup/lv_root > dracut: inactive '/dev/VolGroup/lv_swap' [1.94 GiB] inherit > dracut: inactive '/dev/VolGroup/lv_root' [230.69 GiB] inherit > dracut: PARTIAL MODE. Incomplete logical volumes will be processed. > dracut: Operation prohibited while global/metada...

Hi All, One of my servers upon a restart today comes up with an error checking filesystems: fsck.ext3: no such file or directory while trying to open /dev/VolGroup-1/Logvol00. /dev/VolGroup-1/LogVol00. The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an...

...Welcome to Fedora Press ''I'' to enter interactive startup. Starting udev: [ OK ] Setting hostname localhost.localdomain: [ OK ] mdadm: No arrays found in config file or automatically Setting up Logical Volume Management: 2 logical volume(s) in volume group "VolGroup" now active [ OK ] Checking filesystems Checking all file systems. [/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/mapper/VolGroup-lv_root /dev/mapper/VolGroup-lv_root: clean, 17225/310688 files, 169285/1242112 blocks [/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a /dev/xvda1 /dev/xvda1: clean, 3...

...single disk this works, here is the relevant part from the kickstart file (I shortened the name of the volume group) ... zerombr clearpart --none --initlabel part /boot --fstype="xfs" --label=boot --onpart=vda1 part pv.00 --fstype="lvmpv" --onpart=vda2 --noformat volgroup v --noformat logvol / --fstype=xfs --name=wurzel --vgname=v --useexisting logvol /home --fstype=ext4 --name=home --vgname=v --noformat ... you see, / will be reformatted, /boot will be reformatted, but /home will not. Now a machine with md raid 1. I tried the following. ... #zerombr #clea...

.../boot/grub/grub.conf; the Xen stanza should look something like this: title CentOS (3.18.21-17.el6.x86_64) root (hd0,0) kernel /xen.gz dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all module /vmlinuz-3.18.21-17.el6.x86_64 ro root=/dev/mapper/VolGroup-lv_root rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD rd_LVM_LV=VolGroup/lv_swap SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=VolGroup/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet module /initramfs-3.18.21-17.el6.x86_64.img -George

...es. So now I am looking at the partitioning page and I am surprised to see /dev/sdb and sdb1 down at the bottom, since that disk was *not* selected. I select sdb1 and try to delete, it says " unable to delete You cannot delete this partition: this parition is part of the LVM volume group 'volgroup00'". If I try to delete /dev/sdb1, it says I must choose a partiton. If i try to edit volgroup00, it says 'LVM volume groups can only be edited in the graphical installer." So, am I stuck? It seems like my only option is to go ahead and add both disks, then try to remove one of t...

...a29 (EL8). I get a "device is too small for new format" error. Any hints? part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT part pv.0104 --fstype="lvmpv" --ondisk=sda --grow volgroup ee --pesize=4096 pv.1974 logvol / --fstype="ext4" --size=3072 --encrypted --label="ROOT" --name=00 --vgname=ee logvol /srv --fstype="ext4" --percent=100 --grow --encrypted --label="SRV" --name=01 --vgname=ee Thanks, LF

Hi, These are my make menuconfig screen shots. I haven''t found any xen option in v2.6.30-rc. Why is that so? this happens with most of the version. What should I do? should I just let it as it is an run the make command to build the kernel? Regards, Fasiha Ashraf See the Web''s breaking stories, chosen by people like you. Check out Yahoo! Buzz. Love Cricket?

...tion but getting a bit stuck. This is what I have: %pre if [ -b /dev/sda ] then zerombr clearpart --all bootloader --location=mbr --timeout=0 --driveorder=sda --append="crashkernel=auto rhgb quiet" part /boot --fstype=ext4 --size=500 part pv.008002 --grow --size=1 volgroup vg_host --pesize=4096 pv.008002 logvol / --fstype=ext4 --name=lv_root --vgname=vg_host --grow --size=1024 --maxsize=51200 logvol swap --name=lv_swap --vgname=vg_host --grow --size=512 --maxsize=1024 fi elif [ -b /dev/vda ] then zerombr clearpart --all bootloader --location=mbr -...

...# LANG=C lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sr0 11:0 1 1024M 0 rom vda 252:0 0 15G 0 disk |-vda1 252:1 0 500M 0 part /boot `-vda2 252:2 0 14.5G 0 part |-VolGroup-lv_root (dm-0) 253:0 0 12.5G 0 lvm / `-VolGroup-lv_swap (dm-1) 253:1 0 2G 0 lvm [SWAP] vdb 252:16 0 40G 0 disk /mnt/extradiskA # mount /dev/mapper/VolGroup-lv_root on / type ext4 (rw,usrquota,grpquota) proc on /proc type proc (rw) sysfs on /sys type sys...

On 04/13/2016 12:02 AM, ???? wrote: > In /etc/rc.d/rc.sysinit, > there's "mount -a -n -t nonfs,nfs4,smbfs,ncpfs,cifs,gfs,gfs2i,glusterfs -O > no_netdev". > > > I have other same type servers. And on other servers with same /etc/fstsb, > file system is correct. > There's no difference between normal server's rc.sysinit and this problem > server's