similar to: KVM raw on DRDB on LVM logical volume?

Hi All, I''m successfully using drbd on xen dom0''s across a 2 machine cluster. However I have one domU that refuses to start on one of the machines, but starts find on the other. Config files for domU and drbd are identical. Not sure where to start looking to diagnose the problem x-host-3:/etc/xen # xm create n-monitor Using config file "/etc/xen/vm/n-monitor".

Hi all, i?m not sure if my problem is realted to ocfs2 or to drbd, so i x-post this post to both lists. I?ve drbd-volume [v 8.3.9] (dual-primary) with ocfs2 [v 1.6.3] as a filesystem. If I add a "bind-mount" like /var/log/ispconfig/httpd/blog.schaal-24.de /srv/www/clients/client2/web323/log none bind,nobootwait 0 0 to /etc/fstab i`m unable to run umount /srv/www (which is

Under xen, either stock xen-2.0.1+linux-2.6.9 or Fedora''s latest (2.6.10-1.1109_FC4), drdb (<http://www.drbd.org/>),as soon as I try to write to one of its devices, causes "Badness" in the kernel and, ultimately, a spontaneous reboot. Under non-xen 2.6.10-1.1109_FC4 and 2.6.9-1.678_FC3, drbd works fine. The error: Jan 25 21:01:23 turing kernel: Badness in blk_plug_device

Hi. The short story... Rush job, never done clustered file systems before, vlan didn't support multicast. Thus I ended up with drbd working ok between the two servers but cman / gfs2 not working, resulting in what was meant to be a drbd primary/primary cluster being a primary/secondary cluster until the vlan could be fixed with gfs only mounted on the one server. I got the single server

Hej folks, I''m messing around with DRBD once again but with a new Xen 4.1.2 installation using the XL toolstack instead of the xend daemon. However, after getting my DRBD installed and a device operational, trying to create a domU using the drbd block device doesn''t want to work: xl create -c test.cfg Parsing config file test.cfg Unknown disk type: drbd My config has: disk

Hi, on our samba 4 domain member server we use the vfs objects module 'recycle'. Unfortunately we ran into a strange permission problem with deleted folders. The newly created folders in the recycle folder have the wrong permission. The deleted file(s) itself has the correct group (rw) permissions. The shares correct permissions: getfacl Papierkorb/ # file: Papierkorb/ # owner: root #

Hi all, Where i want to arrive: 1) having two storage server replicating partition with DRBD 2) exporting via GNBD from the primary server the drbd with GFS2 3) inporting the GNBD on some nodes and mount it with GFS2 Assuming no logical error are done in the last points logic this is the situation: Server 1: LogVol09, DRDB configured as /dev/drbd0 replicated to Server 2. DRBD seems to work

Hi, we are in the process of testing a migration from our NT Classic Domain with OpenLdap to Samba AD. In our test setup migration of all accounts, groups and computer accounts went well using the classicupgrade path. Next step now is testing how to add a member server for file server services. We were able to get the server to join the domain and also idmapping works mostly as expected.

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-4 Severity: normal Rebooting from inside domU hangs in initrd: Begin: Waiting for root file system... ... Root file system is not available because underlying DRBD device got deactivated during reboot: $ cat /proc/drbd version: 8.0.13 (api:86/proto:86) GIT-hash: ee3ad77563d2e87171a3da17cc002ddfd1677dbe build by phil at fat-tyre, 2008-08-04

Setup a DC using 4.0.3 - all appears to go fine... Setup a second DC and everything works fine to here...but I'm not sure if replication is actually working or not. Here's what I get from ./samba-tool drs showrepl I've also done. [./samba-tool drs kcc -Uadministrator dc2.samba.somedom.local] in an attempt to fix the replication problem. (or what I think is a problem.) [The outbound

Hello, what would be the easiest and fastest way to migrate a file based DomU to a LVM based DomU. Given that the file contains a partition table + partitions. I tried with an dummy approach: dd if=/path/to/file.img of=/dev/volumegroup/logical-volume. That gives me a logical volume that xm create refuses to use.... Reinhard _______________________________________________ Xen-users mailing

I have an 8-core SuperMicro Xeon server with CentOS 6.3. The OS is installed on a 120 GB SSD connected by SATA, the machine also contains an Areca SAS controller with 24 drives connected. The motherboard is a SuperMicro X9DA7. When I installed the OS, I used the default options, which creates an LVM volume group to contain / and /home, and keeps /boot and /boot/efi outside the volume group.

I have a centos 5.6 server that has xen domUs installed on their on logical volumes. These logical volumes contain their own volume groups and again their own logical volumes. I want to access the domU logical volumes and tried this: [root at kr ~]# fdisk -l /dev/VolGroup00/LogVol02 Disk /dev/VolGroup00/LogVol02: 274.8 GB, 274877906944 bytes 255 heads, 63 sectors/track, 33418 cylinders Units =

Hi all, we have followed the very good HOWTO by http://wherethebitsroam.com/blogs/jeffw/drbd-xcp-05 and set up DRBD on XCP 1.1 in primary/primary mode. It works fine, but I am wondering how to squeeze more performance out of the system (we currently use a crossover GB Ethernet connection). When writing a 1 GB file on a guest I get write performance of about 5MB/s (idle). We have disabled all

Hi, i''ve a problem with drbd 0.7.10 module on an xenU OS (testing). I''ve compiling drbd with "make clean all" then "make install" without error. modprobe drbd OK with no error too and now and trying to start drdb /etc/init.d/drbd start Starting DRBD resources: can not open /dev/drbd0: No such device or address [ d0 can not open /dev/drbd0: No such device

I'm running CentOS 4.4 and drbd 0.7 with ext3 filesystems on the drbd device. I'm very interested in moving to drbd 0.8 and pulling my all of my drbd devices into one lvm for greater flexibility in filesystems. I've seen some notes on doing this but wonder if anyone on this list has a cookbook for doing this. Also noted that on the drbd site the only packages they have are set

Hello. I'm trying to perform a classic upgrade from Samba 3.6.6 with LDAP backend on Debian to 4.1.6 on Ubuntu on a new machine. The samba-tools creates the following *smb.con*f: *# cat /etc/samba/smb.conf** *[global] workgroup = SOMEDOM realm = somedom.local netbios name = SOMEDOM server role = member server passdb backend = samba_dsdb server

Hi there First of all apologies for the lenghty message, but it's been a long weekend. I'm trying to setup a two node cluster with the following configuration: OS: Debian 6.0 amd64 ocfs: 1.4.4-3 ( debian package ) drbd: 8.3.7-2.1 lvm2: 2.02.66-5 kernel: 2.6.32-45 mdadm: 3.1.4-1+8efb9d1+squeeze1 layout: 0- 2 36GB scsi disks in a raid1 array , with mdadm. 1- 1 lvm2 VG above the raid1 ,

I tried to create a domain with drbd based disk as the backend "drbd:<resourcename>,..," and I get a "unknown disk type" error. I can spin out a patch if needed, but just wanted to know apriori if this was left out for any specific reason. shriram _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Regardless of the filesystem (i''ve used reiserfs, xfs, ext3), whenever I mount a fresh DRBD partition I get some nasty kernel messages. This is under Debian Sarge, Xen kernel 2.6.11.12-xen0 (dom0) using DRBD v0.7.11 (pulled from Debian "testing"). This is what I did to create the partition. On both nodes I created a new LVM storage device and started DRBD: # lvcreate