search for: vg

...m | 2 +- v2v/Makefile.am | 2 +- 36 files changed, 58 insertions(+), 58 deletions(-) diff --git a/align/Makefile.am b/align/Makefile.am index 4ecbf7e..ed59c7a 100644 --- a/align/Makefile.am +++ b/align/Makefile.am @@ -98,4 +98,4 @@ TESTS += \ endif check-valgrind: - $(MAKE) VG="$(top_builddir)/run @VG@" check + $(MAKE) VG="$(top_builddir)/run $(VG)" check diff --git a/builder/Makefile.am b/builder/Makefile.am index eb6295a..843bac1 100644 --- a/builder/Makefile.am +++ b/builder/Makefile.am @@ -245,7 +245,7 @@ TESTS += test-virt-builder.sh endif ENABL...

Hey Roger, I am seeing this weird behavior when using #linux-next + stable/for-jens-3.8 tree. Basically I can do ''pvscan'' on xvd* disk and quite often I get checksum errors: # pvscan /dev/xvdf PV /dev/xvdf2 VG VolGroup00 lvm2 [18.88 GiB / 0 free] PV /dev/dm-14 VG vg_x86_64-pvhvm lvm2 [4.00 GiB / 68.00 MiB free] PV /dev/dm-12 VG vg_i386-pvhvm lvm2 [4.00 GiB / 68.00 MiB free] PV /dev/dm-11 VG vg_i386 lvm2 [4.00 GiB / 68.00 MiB free] PV /dev/sda VG guests...

Since we switched to using parallel tests, our valgrind tests would definitely have found leaks in the /usr/bin/env program if it had any. Not so much in some of our own programs. Let's fix that. Rich.

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2168506 This small set covers the new /dev/mapper/VG-LV "--key" ID format in the LUKS-on-LVM virt-inspector test. Thanks, Laszlo Laszlo Ersek (3): update common submodule inspector: rename VGs and LVs in LUKS-on-LVM test inspector: test /dev/mapper/VG-LV translation in LUKS-on-LVM test common...

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2168506 This small set covers the new /dev/mapper/VG-LV "--key" ID format in the libguestfs LUKS-on-LVM inspection test. Thanks, Laszlo Laszlo Ersek (3): update common submodule LUKS-on-LVM inspection test: rename VGs and LVs LUKS-on-LVM inspection test: test /dev/mapper/VG-LV translation common...

...S 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 --- PV Name /dev/sda VG Name volgroup_001 PV Size 298.09 GB [625142448 secs] / NOT usable 32.19...

...am very satisfied with it. But now I have the following problem: I have a filesystem on a LV which is in use - files are created, modified and so on. To do a backup I'd like to create a snapshot of this volume which gets backup'd and then dropped. # lvcreate -s -L 20M -n snapshot /dev/vg/data lvcreate -- WARNING: the snapshot will be automatically disabled once it gets full lvcreate -- INFO: using default snapshot chunk size of 64.00 KB for "/dev/vg/snapshot" lvcreate -- doing automatic backup of "vg" lvcreate -- logical volume "/dev/vg/snapshot" s...

I'm working on a quick tutorial for my students, and was planning on using Mann-Whitney U as one of the tests. I have the following (fake) data grade <- c("MVG", "VG", "VG", "G", "MVG", "G", "VG", "G", "VG") sex <- c( "male", "male", "female", "male", "female", "male", "female", "male", &q...

These are my thoughts on adding a test harness to run tests instead of using automake. The aim of this exercise is to allow us to run the full test suite on an installed copy of libguestfs. Another aim is to allow us to work around all the limitations and problems of automake. The first patch makes an observation that since the ./run script sets up $PATH to contain all the directories

If I add VG with some other lv-s to libvirt pool then libvirt slow responding. How to fix it? <pool type='logical'> <name>LVM_MAIN</name> <uuid>a2713bed-ad4a-fb79-83b5-65a9e8f1094e</uuid> <capacity>0</capacity> <allocation>0</allocati...

...d those have a 2TB LUN size limit. So, even though my EMC Clariion arrays can deal with 10TB LUNs without issue, the VMware ESX and all of its guests cannot. So, I have a lot of RDMs for the guests. The backup server's LVM looks like this: [root at backup-rdc ~]# pvscan PV /dev/sdd1 VG vg_opt lvm2 [1.95 TB / 0 free] PV /dev/sde1 VG vg_opt lvm2 [1.95 TB / 0 free] PV /dev/sdf1 VG vg_opt lvm2 [1.95 TB / 0 free] PV /dev/sda2 VG VolGroup00 lvm2 [39.88 GB / 0 free] PV /dev/sdg1 VG bak-rdc lvm2 [1.95 TB / 0 free] PV /dev/sdh1...

This only affects non-HostVG volume groups. rhbz#733578 Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/storage.py | 14 +++++++++++--- 1 files changed, 11 insertions(+), 3 deletions(-) diff --git a/scripts/storage.py b/scripts/storage.py index 5f7f0e3..047bcd1 100644 --- a/scripts/storage.py +++ b/scr...

...Mac text file in a text editor on the PC and save it under a different name, the problem goes away. I have tried this with a half dozen different files. > tmp1<-read.table("deadFly.txt", header=T) > tmp1[1:10,] VTrt Dead.X Dead.C Live.X Live.C N.X N.C P.Live.X P.Live.C 1 Vg 2 0 7 10 9 10 0.78 1.000 2 Vg 5 1 5 8 10 9 0.50 0.890 3 Vg 0 0 8 10 8 10 1.00 1.000 4 Vg 0 0 9 9 9 9 1.00 1.000 5 g 1 1 9 7 10 8 0.90 0.8...

...at /usr/local/vm_creator/workspace/images/fedora #This Configuration file is Automatically Generated on Tue Feb 12 19:33:17 IST 2008 kernel = "/boot/vmlinuz-2.6.16.33-xen" memory = 256 extra = "fastboot" ramdisk = "/boot/initrd-2.6.16.33-xen.img" disk = [''phy:vg/fedora,sda6,w'',''phy:vg/compswap,sda7,w'', ''phy:vg/modules,sda5,r''] name = "fedora.compnode.grid" root = "/dev/sda6 ro" vif=[''bridge=xenbr0''] The logical volumes look like [root@g40 ~]# lvs LV VG Attr LSi...

...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 1). If I go back to the old kernel everything boots fine. On the new kernel only the VG on sdc is seen by LVM. 1. How do I persuade the new kernel to notice the VG with my root partition on it. 2. If #1 is not pos...

In the case where there are multiple volume groups with the same name, the only way to differentiate is with the uuid. Now we will compare uuid's so we don't report the the vg spans multiple disks when it's a duplicate id. Signed-off-by: Mike Burns <mburns at redhat.com> --- scripts/ovirt-config-storage | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/ovirt-config-storage b/scripts/ovirt-config-storage index 8d59a6b..9d8c4...

...sure if this is the right place to ask, but it's worth a shot. I have installed CentOS 6.5 on one of our servers, and have just installed SolusVM. I have also set up LVM, with a PV on /dev/sda4 (which is GPT formatted, and 3.12TB is size). The problem I'm having is that when I create the VG, it will not show up under /dev/<VG-name>, which it's supposed to according to Red Hat guides on LVM. On a CentOS 5.9 server, with an almost identical set up, the VG showed up under /dev/ correctly, so I'm wondering if the VG folder is stored elsewhere in CentOS 6? I have tried the o...

...a way to run lme() so it is a lot faster. The inner loop, j in 1:15000, takes about 2 hrs on my 2.8GHz dual Xeon 4GB RAM machine. The timings I have done show the dominant execution time is in lme. options(contrasts=c("contr.sum", "contr.sum")) getOption("contrasts") vg <- c(1,2,1,2,2,1,2,1,1,2,1,2,2,1,2,1,1,2,1,2,2,1,2,1) ag <- c(1,1,1,1,2,2,2,2,3,3,3,3,4,4,4,4,5,5,5,5,6,6,6,6) dy <- c(1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2) rp <- c(1,1,1,1,1,1,1,1,2,2,2,2,2,2,2,2,3,3,3,3,3,3,3,3) for (perm in 1:216){ vg <- vgAll[perm,] for(j in 1:1...

Hello, I have this in my dialplan : exten => s,n,Set(vgLabel=vg(${number}+1)) exten => s,n,GoTo(${vgLabel}) But in stead of vgLabel becoming the SUM of 2 numbers, it is just a string : [Nov 3 16:17:27] -- Executing [s at macro-f:43] Set("SIP/test-00000002", "vgLabel=vg(1+1)") in new stack [Nov 3 16:17:27] -- Executing...

...~300Gig. My question is: what happens to the LVM Volume Group? Will it grow when the RAID array grows? Or should I leave /dev/md1 its current size and create a new RAID array and add this as a second PV and grow the Volume Group that way? The documentation is not clear as to what happens -- the VG is marked 'resisable'. sauron.deepsoft.com% sudo pvdisplay --- Physical volume --- PV Name /dev/md1 VG Name sauron PV Size 148.09 GB / not usable 768.00 KB Allocatable yes PE Size (KByte) 4096 Total PE 37...