How to compile DRBD RPM for XenServer 6.0

A few quick notes on compiling your own DRBD RPM for XenServer 6.0

1. Download the latest XenServer DDK ISO – Available from Citrix.com

2. Mount or Extract the ISO – Import into XenServer as a VM

3. Make sure you add a network connection

4. SSH onto the VM

You need to install gcc and libxslt to compile DRBD

> yum –enablerepo=base -y install gcc libxml2.i386 libxslt.i386

> mkdir drbd

> cd drbd

> wget http://oss.linbit.com/drbd/8.4/drbd-8.4.1.tar.gz

> tar -xvf drbd-8.4.1.tar.gz

> cd drbd-8.4.1.tar.gz

> ./configure

> make km-rpm

> make rpm

RPM file are created in /usr/src/redhat/RPMS/i386/

You need,

drbd-km-2.6.32.12_0.7.1.xs6.0.0.529.170661xen-8.4.1-1.i386.rpm
drbd-utils-8.4.1-1.i386.rpm

Thats it enjoy!

6 thoughts on “How to compile DRBD RPM for XenServer 6.0

  1. Hi JoeI want to warn everybody of this Linbit news and the WARNING in it contained.With regardsRobert @ http://www.nas-datarecovery-raid.comDRBD 8.4.2 Has been ReleasedFor any user of DRBD-8.4, we suggest an upgrade to 8.4.2 as changes to the kernel in version 2.6.36 or newer have caused an issue that may cause data corruption on a Secondary/Sync target when using protocols A or B. (In the 8.3 series this was already fixed with the 8.3.13 release).It is worth noting that all previous DRBD releases did not enforce correct ordering of (some) write operations on a resync-target node. It is a rare condition that could trigger the potential data corruption. It may cause corruption in the sense that it looks like if a single block write was not executed on the secondary. Actually it was overwritten with the previous version of the data. This second write originates from the resync process.Apart from that those nasty bugs, we have also fixed a condition where "disk-barrier no" and "disk-flushes no" were ineffective. This was the reason why some people were reporting "drbd-8.3 is faster than drbd-8.4". You can read all the details here. There are also several new features in this release:1) New option ‘al-updates no’ to disable writing transactions into the activity log. It is useful for improved performance of a spread out random write work load. It will require a full sync after a primary crash2) Expose the data generation identities via sysfs3) "–stop" option for online verify to specify a stop sector

Leave a Reply

Your email address will not be published. Required fields are marked *