similar to: LVM2 snapshots and XEN = problem :(

Hi... I have had a problem when I am going to detach one specific LVM partitions of Xen, so I have been trying xm destroy <domain>, lvchange -an <lvm_partition>, lvremove -f.... So I haven''t had sucess. I restarted the server with init 1 yet and nothing... I have seem two specific process started xenwatch and xenbus, but I am not sure if this processes have some action over

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

hi, I use the libvirt-python to manage my virtual machine. When I delete a volume use vol.delete(0), sometimes it note me that has occur the error: libvirtError: internal error '/sbin/lvremove -f /dev/vg.vmms/lvm-v097222.sqa.cm4' exited with non-zero status 5 and signal 0: Can't remove open logical volume

Just discovered that on CentOS 4.1 when you issue the command: lvcreate -s -n temp -L2G /dev/vgname/lvname to create a snapshot, you get the error message: snapshot: Required device-mapper target(s) not detected in your kernel I've checked and recheck my spelling and tried using the device created under /dev/mapper. I've tried it on both x86_64 and on i386. Works as expected under

Hi I read a few times in the web about xen-3.0.2-3 but I cannot find a place to download it. Not even here: http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/ Where can I get it? And does it have network issues solved? And what is the most current kernel I can use with xen? How do I change the source to use a more current kernel than 2.6.16.6? Regards, Steffen Please - if possible

Hello guys I have the following problem with xen 3.0.1 compiled from sources on Debian Sarge, kernel 2.6.12.6 which can be easily reproduced at least on my installation: after I log in to domU console or via ssh and run "shutdown" I get deadlocked network interface with error message: unregister_netdevice: waiting for vifX.0 to become free. Usage count = n After this happen I

Hello, this is my first time posting on this mailing list. I wanted to suggest a addition to the qemu hook. I will explain it through my own use case. I use a shared LVM storage as a volume pool between my nodes. I use lvmlockd in sanlock mode to protect both LVM metadata corruption and concurrent volume mounting. When I run a VM on a node, I activate the desired LV with exclusive lock

Hi, I am trying to manually install libvirt 1.2.7 on Ubuntu 12.04 LTS (64bit). I have installed libxml2-dev libgnutls-dev libcurl4-gnutls-dev python-dev, but I am facing dependency issues for libdevmapper libraries. ​ ​Is there any workaround for this dependency​? OR is there any other way to install libivirt 1.2.7 on Ubuntu 12.04. ​ ​Following is the output of the error​ #apt-get install

I've upgraded my x86_64 4.2 box to the latest kernel 2.6.9.34 and tried an lvm snapshot. It worked fine and I was able to mount the snapshot etc. Now I cannot seem to remove the snapshot. If I try a 'lvremove' it asks if I want to remove the 'active' snapshot, if I say yes it just hangs and the box goes to 99% wait io, however the disk lights do not come on during this. The

Hi all I''d like to know if it''s possible to clone a running domU. I need to make an exact copy of an existing CentOS xen domU, but without taking it offline. I''m using LVM, so I don''t know if it will help. I have tried doing it with dd, after shutting down the domU, but it takes ages. The LVM image is 30GB. I can''t really afford to have the

Hello, When I want to install libvirt-0.10.0 from source, I get this error at the configure stage checking for libdevmapper.h... no configure: error: You must install device-mapper-devel/libdevmapper >= 1.0.0 to compile libvirt However the package is installed on my system # yum list device-mapper-libs.x86_64 Installed Packages device-mapper-libs.x86_64                               

Thank for your answer: But i dont know understand why is following not working: I want to restrict the ssh access for a special domain member: In my "sshd_config" i added: AllowGroups restrictaccess root With user2 im able to login via ssh! log: pam_krb5(sshd:auth): user user2 authenticated as user2 at ROOTRUDI.DE With user1 im not! log: User user1 from 192.168.0.100 not allowed

Hi, I want to rename some volume groups and logical volumes. I was not surprised when it would not let me rename active volumes. So I booted up the system using the CentOS 5.5 LiveCD, but the LiveCD makes the logical volumes browsable using Nautilus, so they are still active and I can't rename them. Tried: /usr/sbin/lvchange -a n VolGroup00/LogVol00 but it still says: LV

I could launch `lvchange -asy` on the source host manually, but the aim of hooks is to automatically execute such commands and avoid human errors. Le 22 janvier 2020 09:18:54 GMT+01:00, Michal Privoznik <mprivozn@redhat.com> a écrit : >On 1/21/20 9:10 AM, Guy Godfroy wrote: >> Hello, this is my first time posting on this mailing list. >> >> I wanted to suggest a

Hi, I just installed a CentOS 6.5 System with the intention of using thinly provisioned snapshots. I created the volume group, a thinpool and then a logical volume. All of that works fine but when I create a snapshot "mysnap" then the snapshot volume gets displayed in the "lvs" output with the correct information but apparently no device nodes are created under

Dear all, I'm rather new to glusterfs but have some experience running lager lustre and beegfs installations. These filesystems provide active/active failover. Now, I discovered that I can also do this in glusterfs, although I didn't find detailed documentation about it. (I'm using glusterfs 3.10.8) So my question is: can I really use glusterfs to do failover in the way described

hi, My volume group is vg. Inside that i have around 10 lvm partitions (each of 100GB). When I try to remove partitions using lvremove /dev/vg/lvm1 It acts like the machine freezes and after a long time the lvremove process gets killed saying "Killed" Whats wrong here. I don't see anything interesting in /var/log/message Thanks Paras.

At the beginning of January I encountered a problem where several vm guests on a single host somehow managed to see the the virtual disks assigned to other guests on the same hosts. I was unable to resolve this situation and shutdown the affected guests after creating new guest instances and moving the services and data off the corrupted guests. I have since removed these guests via virt-manager

At the beginning of January I encountered a problem where several vm guests on a single host somehow managed to see the the virtual disks assigned to other guests on the same hosts. I was unable to resolve this situation and shutdown the affected guests after creating new guest instances and moving the services and data off the corrupted guests. I have since removed these guests via virt-manager

I'm having some difficulty finding a method to shrink my /home to expand my /.? They both correspond to LVMs.? It is my understanding that one cannot shrink a xfs filesystem.? One must back it up (xfsdump), remove (lvremove) redefine it and then restore it back (xfsrestore). Okay, I'm running into a problem where /home? needs to be "unused".? If tried going in to