similar to: Cannot remove lvs associated with deleted vm guests

On Mon, January 16, 2012 17:01, Dennis Jacobfeuerborn wrote: > On 01/16/2012 10:16 PM, James B. Byrne wrote: > > ... >> The xmldump for this guest instance contains this: > ... > > Please post the xmldumps of the original guest and cloned > guest right after > cloning and without any modifications. > > Regards, > Dennis Prototype dumpxml virsh # dumpxml

Are folks in the Centos community succesfully using device-mapper-multipath? I am looking to deploy it for error handling on our iSCSI setup but there seems to be little traffic about this package on the Centos forums, as far as I can tell, and there seems to be a number of small issues based on my reading the dm-multipath developer lists and related resources. -geoff Geoff Galitz Blankenheim

The following patches introduce support for multipath and cciss devices to the ovirt-node and node-image. Comments are appreciated. These patches assume that the 3 patches (2 node, 1 node-image) from Joey are all incorporated. Mike

I mistyped the storage allocation for an additional virtio drive for one of our vm guests and now I cannot get rid of the thing. I have discovered that this is probably, indeed almost certainly, related to udev but the few work arounds I have found all seem to fail for me. Does anyone here know how to remove these things? When I try this: # for i in {1..200}; do udevadm control

All other patches from the sequence remain unchanged. Repost of patch 6 based on comments from Joey to follow. Mike

This set of patches introduces support for multipath devices for storage. Comments and suggestions are appreciated. Mike

OS CentOS-6.2 with updates to present. I use git on this host to manage configuration changes and to monitor package alterations. This is not meant to be a security check. It is simply a way for me to easily recover from fumble fingered configuration changes. Yesterday git status reported that the following files had changed since the previous commit: # modified: ../usr/bin/gdb #

Has anyone set up any form of apache user isolation on CentOS? I have multiple virtual hosts on my machine, run by users who do not trust eachother. The problem is that any php script run by apache is able to do things like raw file io on other users' .htpasswds, php scripts, hidden directory listings, and so on. Database passwords can even be divulged in this way, since they are often stored

CentOS-6.2 I created a new VirtIO disk for one of my virtual machines. Previous experience has taught me that I need to partition it before attempting to add the new storage to the physical volume set of the intended guest. Up to now I have simply accepted the defaults given by fdisk after telling it that I want a new partition. The defaults always exclude the first 2048 sectors. Disk

Hello, can someone explain these errors Oct 27 15:34:05 vhost01 named[1316]: zone #ZONE#/IN/auth: refresh: retry limit for master IPV6-MASTER#53 exceeded (source IPV6-THIS#0) Oct 27 15:34:05 vhost01 named[1316]: zone #ZONE#/IN/auth: Transfer started. Oct 27 15:34:06 vhost01 named[1316]: zone #ZONE#/IN/auth: refresh: retry limit for master IPV6-MASTER#53 exceeded (source IPV6-THIS#0) Oct 27

Hello, suppose I want to use a special configuration for my IBM/1814 storage array luns, then I put something like this in multipath.conf devices { device { vendor "IBM" product "^1814" product_blacklist "Universal Xport" path_grouping_policy "group_by_prio" path_checker

Hi everyone, This is dm-ioband version 0.0.3 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. Changes since 0.0.2 (23rd January): - Ported to linux-2.6.24. - Rename the name of this device-mapper device as "ioband." - The output format of "dmsetup

Hi everyone, This is dm-ioband version 0.0.3 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. Changes since 0.0.2 (23rd January): - Ported to linux-2.6.24. - Rename the name of this device-mapper device as "ioband." - The output format of "dmsetup

Hi everyone, This is dm-ioband version 0.0.3 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. Changes since 0.0.2 (23rd January): - Ported to linux-2.6.24. - Rename the name of this device-mapper device as "ioband." - The output format of "dmsetup

Hi everyone, I'm happy to announce that I've implemented a Block I/O bandwidth controller. The controller is designed to be of use in a cgroup or virtual machine environment. The current approach is that the controller is implemented as a device-mapper driver. What's dm-band all about? ======================== Dm-band is an I/O bandwidth controller implemented as a device-mapper

Hi everyone, I'm happy to announce that I've implemented a Block I/O bandwidth controller. The controller is designed to be of use in a cgroup or virtual machine environment. The current approach is that the controller is implemented as a device-mapper driver. What's dm-band all about? ======================== Dm-band is an I/O bandwidth controller implemented as a device-mapper

Hi everyone, This is dm-ioband version 0.0.4 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. Changes since 0.0.3 (5th February): - Improve the performance when many processes are issuing I/Os simultaneously. - Change the table format to fully support dmsetup

Hi everyone, This is dm-ioband version 0.0.4 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. Changes since 0.0.3 (5th February): - Improve the performance when many processes are issuing I/Os simultaneously. - Change the table format to fully support dmsetup

Hi everyone, This is dm-ioband version 0.0.4 release. Dm-ioband is an I/O bandwidth controller implemented as a device-mapper driver, which gives specified bandwidth to each job running on the same physical device. Changes since 0.0.3 (5th February): - Improve the performance when many processes are issuing I/Os simultaneously. - Change the table format to fully support dmsetup

Hi All, My CentOS 5.1 server is using iSCSI attached disks connecting to a dual controller storage array. I have also configured multipathd to manage the multiple paths. Everything works well, and on boot the dev nodes are automatically created in /dev/mapper. On these devices, I have created logical volumes using lvm2. My problem is that lvm does not recognize these iscsi/multipath volumes on