similar to: anaconda, kickstart, lvm over raid, logvol --grow, centos7 mystery

On Wed, May 25, 2011 at 12:41 AM, JAMES BOND 123 007 <james123007@gmail.com> wrote: > Hi , > I saw your thread post at > http://web.archiveorange.com/archive/v/ZvO4jnaavtTfcyqnHoRX > , about problems with XEN 4.0 installation. > I have the same problem and my machine is similar to yours( HP Proliant > DL380G6, 4GB-RAM) This question is better asked on the xen-users list.

Hi, Sorry for the need of the long winded email. Looking for some answers to the following. I am setting up a xen PV domU on top of a LVM partitioned DRBD device. Everything was going just fine until I tried to test the filesystems in the domU. Here is my setup; Dom0 OS: CentOS release 5 (Final) Kernel: 2.6.18-8.1.4.el5.centos.plusxen Xen: xen-3.0.3-25.0.3.el5 DRBD:

Hello Group, I am building a company application based on Centos 5.7 OS. The application was working earlier and creating right partitions both for hardware as well as VM. But since we introduced Centos 5.7 OS and start building application with 5.7 anaconda the hardware partitions are duplicate of VM partitions *while creating hardware partition my code looks like.* cat >

Hi guys, I followed this article to install my first xen project to compare its CPU/memory and I/O performance with a kvm domain on CentOS 6.4. http://www.virtuatopia.com/index.php/Building_a_Xen_Virtual_Guest_Filesystem_on_a_Disk_Image_%28Cloning_Host_System%29 In the initial tests whit super.pi benchmarck the CPU performance of my xen domai was extremely worst than my kvm domain. Well, I am

Has anyone managed to create an encrypted disk partition with CentOS 8 kickstart? 1 reqpart --add-boot 2 part /boot --fstype ext3 --size=1024 --ondrive=sda 3 part pv.1 --size=1 --grow --ondrive=sda --encrypted --pashphrase="bla" 4 volgroup vol0 pv.100000 5 logvol / --vgname=vg_00 --name=lv_root --size=102400 --fstype=ext4 ... No matter what I specify in line 3, the installer bombs out.

I'm using the kickstart file we developed for v5 on 6.2 in VM (kvm/qemu running on a CentOS 5.6), but it fails: Error partitioning. Could not allocate requested partitions: not enough free space on disks. There's nothing wrong with the disk. Both fdisk and parted works fine, I can view, partition and write a partition table and the disk is 10.5GB. However, looking through

Does anyone know how anaconda partitioning enumerates disk partitions when specified in kickstart? I quickly browsed through the anaconda installer source on github but didn't see the relevant bits. I'm using the centOS 6.10 anaconda installer. Somehow I am ending up with my swap partition on sda1, /boot on sda2, and root on sda3. for $REASONS I want /boot to be the partition #1 (sda1)

Hello All, I finally compiled xen 3.3.0 using make World, installed it but I cannot get it to Boot, I always get kernel panic, kernel not sync kind of errors, I suppose it''s some hard disk or partition issue, my setup is as follows. CentOS 5.2 x86_64 on a HP ML-115 Grub, menu.list Entries CentOS xen''s line title CentOS (2.6.18-92.1.22.el5xen) root

Hi all. I have currently a server: cat /etc/redhat-release CentOS release 5.7 (Final) uname -a Linux host.domain.com 2.6.18-274.18.1.el5 #1 SMP Thu Feb 9 12:45:44 EST 2012 x86_64 x86_64 x86_64 GNU/Linux I have there a filesystem mounted: /dev/vg0/paczki /home/paczki-workdir ext4 defaults,noatime 0 0 on which df gives strange output: LANG=C df -h

I am not sure if it''s a xen bug or lvm bug, or just my bad hardware, but here''s how to reproduce: /dev/vg0/centos1 is lvm block used by a domainU, it''s 8G in size. #lvcreate -L8192M -s -n snap1 vg0 #mount /dev/vg0/snap1 /mnt do some copying files here #umount /mnt #lvremove /dev/vg0/snap1 not removed! it says can''t allocated memory #xm mem-set 0 512 #lvremove

Hi! I'' ve a xen virtual machine, and i'' d like to assign cdrw device to it. My physical device on domain0 is /dev/hda, and in the configuration file i'' ve this: disk = [ ''phy:vg0/vx-disk,sda1,w'', ''phy:vg0/vx-swap,sda2,w'', ''phy:vg0/vx-data,sda5,w'' ] I'' ve tried to assign the cdrom to it in many ways i

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there some limit on the size of a file system which can be shared via samba? I'm trying to set up a file server with a 100GB shared partition and it doesn't want to work. I'm running Fedora Core 4, and Samba Version 3.0.14a-2. The output from testparm looks like this: [root@stitch samba]# testparm Load smb config files from

Hello list. I have a perfectly working PV host, with this configuration: kernel = "/boot/vmlinuz-2.6.18.8-xen-3.3.0-7mdv" ramdisk = "/boot/initrd-2.6.18.8-xen-3.3.0-7mdv.img" root = "/dev/sda1 ro" extra = "(hd0)/boot/grub/menu.lst" memory = 256 maxmem = 512 name = "sexonthebeach" uuid = "f36962f5-0dec-4708-84a0-f5b4dea48d34" disk = [

Hi! I am using xen-tools version: 3.9-4 to create domUs: 1. time xen-create-image --verbose --dist=lenny --install-source=/mnt/xen-file-images/lenny-64-template-debootstrap-30Jun09-fix2.tar --hostname dummy --ip xxx.xxx.xxx.xxx --force 2. xm create dummy.cfg Then I get the message Device /dev/vg0/dummy-disk is mounted in the privileged domain, and so cannot be mounted by a guest. 3. When I

On Sun, 21 Aug 2016 at 12:51 Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/19/2016 11:35 PM, Phil Manuel wrote: > > The install fails under UEFi due to the fact the partitions are not > cleared, and it doesn?t have any space to continue. Is there an extra step > I need to do to remove the original partitions before the new layout will > work ? > > >

Hello, I am having trouble expanding a volume. Every time I try to add bricks to the volume, I get this error: [root at gluster1 sdb1]# gluster volume add-brick vg0 gluster5:/export/brick2/sdb1 gluster6:/export/brick2/sdb1 /export/brick2/sdb1 or a prefix of it is already part of a volume Here is the volume info: [root at gluster1 sdb1]# gluster volume info vg0 Volume Name: vg0 Type:

On 06.07.2017 15:35, Robert Nichols wrote: > On 07/06/2017 04:43 AM, Volker wrote: >> Hi all, >> >> one of my lv has become completely unaccessible. Every read access >> results in a buffer io error: >> >> Buffer I/O error on dev dm-13, logical block 0, async page read >> >> this goes for every block in the lv. A ddrescue failed on every single

'--no-degraded' flag in the first mdadm call inhibits the startup of array unless all expected drives are present. This will prevent starting arrays in degraded state. Second mdadm call (after LVM is scanned) will scan unused yet devices and make an attempt to run all found arrays even they are in degraded state. Two new tests are added. This fixes rhbz1527852. Here is boot-benchmark

I thought I'd test replacing a failed drive in a 4 drive raid 10 array on a CentOS 5.2 box before it goes online and before a drive really fails. I 'mdadm failed, removed', powered off, replaced drive, partitioned with sfdisk -d /dev/sda | sfdisk /dev/sdb, and finally 'mdadm add'ed'. Everything seems fine until I try to create a snapshot lv. (Creating a snapshot lv

Hi all, one of my lv has become completely unaccessible. Every read access results in a buffer io error: Buffer I/O error on dev dm-13, logical block 0, async page read this goes for every block in the lv. A ddrescue failed on every single block. $ lvdisplay --- Logical volume --- LV Path /dev/vg0/lv-vm-tviewer LV Name lv-vm-tviewer VG Name