search for: gndb

...5 (see http://www.centos.org/modules/newbb/viewtopic.php?topic_id=7816&forum=41 for details).. DRBD and heartbeat are working, and now I want to put GNBD on top on this. However, I installed the latest CentOS-plus kernel (2.6.18-8.1.8.el5.centos.plus) but there doesn't appear to be a kmod-gndb for this kernel. Looks like the latest kmod-gnbd is available for kernel 2.6.18-8.1.8.el5. But I cannot find a kmod-drbd for this kernel. Am I missing something or is this worth a entry in the buglist? Tnx! -- We've Got Your Name at http://www.mail.com ! Get a FREE E-mail Account Today - Ch...

Hi all I tried to run bonnie++ disk stresser in dom-U, who''s disk is backed with non-local (on nfs) loop-back file. The machine rebooted pretty quickly. So, how do I tell what''s barfing? Is it Xen? Is it dom-0 (nfs or loop-back)? I looked in dom-0''s /var/log/messages and didn''t see any obvious record of a dom-0 whoopsie (but is that the right place to look

On CentOS 5, the current centosplus kernel doesn't want to play with the kmod-gfs package (because kmod-gfs wants the stock kernel): # yum install kmod-gfs gives me: Transaction Check Error: package kernel-2.6.18-8.1.14.el5.centos.plus (which is newer than kernel-2.6.18-8.1.14.el5) is already installed Should it work, or is there a separate centosplus build that I've not

I have a system with a large LVM VG partition. I was wondering if there is a way i could share the partition using nbd and have the nbd-client have access the LVM as if it was local. SYSTEM A: /dev/sda3 is a LVM partition and is assigned to VG volgroup1. I want to share /dev/sda3 via nbd-server SYSTEM B: receives A''s /dev/sda3 as /dev/nbd0. I want to access it as VG volgroup1. I am

Hi guys, I wonder if anyone has found any simple solution for cheap and cheerful replication between two hosts (in this case for XCP)? Basically I have two machines (A and B). I want to run 8 VMs on local storage on server A and 8 VMs on local storage on server B. I want all the machines on server A to be backed up to server B and vice versa. In the event of failure, I want to be able to run all