Difference between revisions of "DRBD on Fedora 13"

From AN!Wiki
Jump to: navigation, search
(Configure)
(Install)
Line 12: Line 12:
  
 
<source lang="bash">
 
<source lang="bash">
yum -y install drbd.x86_64 drbd-xen.x86_64
+
yum install drbd.x86_64 drbd-xen.x86_64
</source>
+
 
+
== If You're Running Xen From Mercurial ==
+
 
+
The above RPM installs will drag in the Xen 3.4.3 hypervisor and tools. To get back to the Xen 4.0.0 tools, rerun the <span class="code">make install-*</span>.
+
 
+
'''Note''': Change to the directory where you checked out the [[git]] repo.
+
 
+
<source lang="bash">
+
cd xen-4.0-testing.hg
+
make install-xen
+
make install-tools
+
make install-stubdom
+
 
</source>
 
</source>
  

Revision as of 23:22, 25 August 2010

 AN!Wiki :: How To :: DRBD on Fedora 13

Warning: Until this warning is removed, do not use or trust this document. When complete and tested, this warning will be removed.

This article covers installing and configuring DRBD on a two-node Fedora 13 cluster.

Why DRBD?

DRBD is useful in small clusters as it provides real-time mirroring of data across two (or more) nodes. In two-node clusters, this can be used to host clustered LVM physical volumes. On these volumes you can create logical volumes to host GFS2 partitions, virtual machines, iSCSI and so forth.

Install

yum install drbd.x86_64 drbd-xen.x86_64

Configure

We need to see how much space you have left on you LVM PV. The pvscan tool will show you this.

pvscan
  PV /dev/sda2   VG vg01   lvm2 [465.50 GiB / 424.44 GiB free]
  Total: 1 [465.50 GiB] / in use: 1 [465.50 GiB] / in no VG: 0 [0   ]

On my nodes, each of which has a single 500GB drive, I've allocated only 20GB to dom0 so I've got over 440GB left free. I like to leave a bit of space unallocated because I never know where I might need it, so I will allocate 400GB even to DRBD and keep the remaining 44GB set aside for future growth. The space you have left and how you want to allocate is an exercise you must settle based on your own needs.

Next, check that the name you will give to the new LV isn't used yet. The lvscan tool will show you what names have been used.

lvscan
  ACTIVE            '/dev/vg01/lv_root' [39.06 GiB] inherit
  ACTIVE            '/dev/vg01/lv_swap' [2.00 GiB] inherit

We see from the above output that lv_root and lv_swap are used, so we will use lv_drbd for the DRBD partition. Of course, you can use pretty much any name you want.

Now that we know that we want to create a 400GB logical volume called lv_drbd, we can proceed.

Now to create the logical volume for the DRBD device on each node. The next two commands show what I need to call on my nodes. If you've used different names of have a different amount of free space, be sure to edit the following arguments to match your nodes.

On an-node01:

lvcreate -L 400G -n lv_drbd /dev/vg01
  Logical volume "lv_drbd" created

If I re-run lvscan now, I will see the new volume:

lvscan
  ACTIVE            '/dev/vg01/lv_root' [39.06 GiB] inherit
  ACTIVE            '/dev/vg01/lv_swap' [2.00 GiB] inherit
  ACTIVE            '/dev/vg01/lv_drbd' [400.00 GiB] inherit

We can now proceed with the DRBD setup!


 

Any questions, feedback, advice, complaints or meanderings are welcome.
Us: Alteeve's Niche! Support: Mailing List IRC: #clusterlabs on Freenode   © Alteeve's Niche! Inc. 1997-2019
legal stuff: All info is provided "As-Is". Do not use anything here unless you are willing and able to take responsibility for your own actions.
Personal tools
Namespaces

Variants
Actions
Navigation
projects
Toolbox