<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: High-Availability with Fedora, DRBD, Heartbeat and Mon [and Xen]</title>
	<atom:link href="http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/feed/" rel="self" type="application/rss+xml" />
	<link>http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/</link>
	<description>Just another geek blog.</description>
	<pubDate>Fri, 12 Mar 2010 04:14:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Pietro</title>
		<link>http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-168</link>
		<dc:creator>Pietro</dc:creator>
		<pubDate>Thu, 29 Jan 2009 14:22:31 +0000</pubDate>
		<guid isPermaLink="false">http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-168</guid>
		<description>Hi Vic,

I finally re-installed Fedora 9 and followed the guide again exactly how it is written.

However I have stopped again in exactly the same position.
The command: "whereis drbdadm" gave the following output:

drbdadm:

and thats it!  nothing else was shown.
I then proceeded to input (whilst in root):

source ~/.bashrc
source ~/.bash_profile

which gave the output:

/etc/drbd.conf:15: Parse error: '_is_default &#124; ;' expected,
                 but got 'outdate-peer'

I had copied the drbd.conf file as per the guide but obviously its not correct for my particular servers.
So I then re-configured the drbd.conf file to an almost identical copy of what is in Chapter 5 of the drbd.org manual which is this:

global { 
  usage-count yes; 
}
common {
  protocol C;
}
resource r0 {
  on cluster1 {
    device    /dev/drbd1;
    disk      /dev/sda2;
    address   10.10.10.150:7789;
    meta-disk internal;
  }
  on cluster2 {
    device    /dev/drbd1;
    disk      /dev/sda2;
    address   10.10.10.151:7789;
    meta-disk internal;
  }
}

Note: I've used sda2 because I only have 2 partitions due to the fact that nothing was mentioned at the start of this guide to the way the hard drives need to be partitioned, that's why I mentioned the partitioning in the previous post.
Thus I used the standard default partitioning layout scheme when installing Fedora 9.  I noticed that in the guide there are 5 partitions !!! But it didn't mention this anywhere in the guide so I am guessing that there needs to be a particular partitioning layout that needs to be followed when installing Fedora.  Are you able to provide some more information about the partitioning?

Anyway, I found the partitions using the command: /sbin/blkid
And it shows that all of the main data is on sda2 partition and sda1 is the boot partition.

So in any case, it gave the following output (I have 500GB Drives) after I ran drbdadm create-md r0:

You are the 564th user to install this version
md_offset 499348516864
al_offset 499348484096
bm_offset 499333242880

Found LVM2 physical volume signature
Device size would be truncated, which
would corrupt data and result in
'access beyond end of device' errors.
If you want me to do this, you need to zero out the first part
of the device (destroy the content).
You should be very sure that you mean it.
Operation refused.

Command 'drbdmeta /dev/drbd1 v08 /dev/sda2 internal create-md' terminated with exit code 40
drbdadm create-md r0: exited with code 40

- So I'm pretty sure now that it has to do with the partitioning configuration so hopefully you could shed some light on this particular scenario and I am sure it will then turn out perfectly.

Looking very much forward to your reply with great anticipation!

Thanks in Advance :)
Pietro</description>
		<content:encoded><![CDATA[<p>Hi Vic,</p>
<p>I finally re-installed Fedora 9 and followed the guide again exactly how it is written.</p>
<p>However I have stopped again in exactly the same position.<br />
The command: &#8220;whereis drbdadm&#8221; gave the following output:</p>
<p>drbdadm:</p>
<p>and thats it!  nothing else was shown.<br />
I then proceeded to input (whilst in root):</p>
<p>source ~/.bashrc<br />
source ~/.bash_profile</p>
<p>which gave the output:</p>
<p>/etc/drbd.conf:15: Parse error: &#8216;_is_default | ;&#8217; expected,<br />
                 but got &#8216;outdate-peer&#8217;</p>
<p>I had copied the drbd.conf file as per the guide but obviously its not correct for my particular servers.<br />
So I then re-configured the drbd.conf file to an almost identical copy of what is in Chapter 5 of the drbd.org manual which is this:</p>
<p>global {<br />
  usage-count yes;<br />
}<br />
common {<br />
  protocol C;<br />
}<br />
resource r0 {<br />
  on cluster1 {<br />
    device    /dev/drbd1;<br />
    disk      /dev/sda2;<br />
    address   10.10.10.150:7789;<br />
    meta-disk internal;<br />
  }<br />
  on cluster2 {<br />
    device    /dev/drbd1;<br />
    disk      /dev/sda2;<br />
    address   10.10.10.151:7789;<br />
    meta-disk internal;<br />
  }<br />
}</p>
<p>Note: I&#8217;ve used sda2 because I only have 2 partitions due to the fact that nothing was mentioned at the start of this guide to the way the hard drives need to be partitioned, that&#8217;s why I mentioned the partitioning in the previous post.<br />
Thus I used the standard default partitioning layout scheme when installing Fedora 9.  I noticed that in the guide there are 5 partitions !!! But it didn&#8217;t mention this anywhere in the guide so I am guessing that there needs to be a particular partitioning layout that needs to be followed when installing Fedora.  Are you able to provide some more information about the partitioning?</p>
<p>Anyway, I found the partitions using the command: /sbin/blkid<br />
And it shows that all of the main data is on sda2 partition and sda1 is the boot partition.</p>
<p>So in any case, it gave the following output (I have 500GB Drives) after I ran drbdadm create-md r0:</p>
<p>You are the 564th user to install this version<br />
md_offset 499348516864<br />
al_offset 499348484096<br />
bm_offset 499333242880</p>
<p>Found LVM2 physical volume signature<br />
Device size would be truncated, which<br />
would corrupt data and result in<br />
&#8216;access beyond end of device&#8217; errors.<br />
If you want me to do this, you need to zero out the first part<br />
of the device (destroy the content).<br />
You should be very sure that you mean it.<br />
Operation refused.</p>
<p>Command &#8216;drbdmeta /dev/drbd1 v08 /dev/sda2 internal create-md&#8217; terminated with exit code 40<br />
drbdadm create-md r0: exited with code 40</p>
<p>- So I&#8217;m pretty sure now that it has to do with the partitioning configuration so hopefully you could shed some light on this particular scenario and I am sure it will then turn out perfectly.</p>
<p>Looking very much forward to your reply with great anticipation!</p>
<p>Thanks in Advance <img src='http://little.bluethings.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
Pietro</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pietro</title>
		<link>http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-167</link>
		<dc:creator>Pietro</dc:creator>
		<pubDate>Thu, 29 Jan 2009 10:31:39 +0000</pubDate>
		<guid isPermaLink="false">http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-167</guid>
		<description>Hi Vic,

Thank you so much for answering the post.
In the mean time, I decided to start from scratch but this time follow a set partitioning layout for drbd so before I installed the OS, I partitioned everything so the transition would be smooth.

I am now following the post and will let everyone know how it turns out.
I won't provide the output as requested, just yet until I get through the whole setup which will be in about 30 minutes.

Thanks again for the help, its greatly appreciated.</description>
		<content:encoded><![CDATA[<p>Hi Vic,</p>
<p>Thank you so much for answering the post.<br />
In the mean time, I decided to start from scratch but this time follow a set partitioning layout for drbd so before I installed the OS, I partitioned everything so the transition would be smooth.</p>
<p>I am now following the post and will let everyone know how it turns out.<br />
I won&#8217;t provide the output as requested, just yet until I get through the whole setup which will be in about 30 minutes.</p>
<p>Thanks again for the help, its greatly appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vic</title>
		<link>http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-166</link>
		<dc:creator>vic</dc:creator>
		<pubDate>Sat, 24 Jan 2009 16:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-166</guid>
		<description>Pietro--

Please let me know what your system prints out when you type this command:

whereis drbdadm

It is quite possible that when you switched to root, your paths were no longer preserved. This is as easy a fix as typing:

source ~/.bashrc
source ~/.bash_profile

And then your drbdadm command will work.
As for creating the partitions, I did not do anything outside of what this guide shows. I did not use gparted. Lower on the instruction guide, I show how to create the filesystem using mkfs.

Good luck, and please be careful when using partitioning utilities to partition disks that have valuable information on them that is not backed up.</description>
		<content:encoded><![CDATA[<p>Pietro&#8211;</p>
<p>Please let me know what your system prints out when you type this command:</p>
<p>whereis drbdadm</p>
<p>It is quite possible that when you switched to root, your paths were no longer preserved. This is as easy a fix as typing:</p>
<p>source ~/.bashrc<br />
source ~/.bash_profile</p>
<p>And then your drbdadm command will work.<br />
As for creating the partitions, I did not do anything outside of what this guide shows. I did not use gparted. Lower on the instruction guide, I show how to create the filesystem using mkfs.</p>
<p>Good luck, and please be careful when using partitioning utilities to partition disks that have valuable information on them that is not backed up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pietro</title>
		<link>http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-165</link>
		<dc:creator>Pietro</dc:creator>
		<pubDate>Sat, 24 Jan 2009 03:47:25 +0000</pubDate>
		<guid isPermaLink="false">http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-165</guid>
		<description>Thank you very much for this very nice guide.  Its great!!!

However whilst I am using Fedora 9, I got stuck at the command: drbdadm create-md r0
My machine just didn't recognise this command by giving the error message: "command not found"

Would you be able to shed some light on a reason why this may be happening?

I know I haven't given much information about it but basically I followed your guide step by step and its perfect until the part where I need to enter: "drbdadm create-md r0"

Also, when I try to partition as per your guide, using gparted, the system doesn't recognise the partitions in Fedora9 which is strange to me.  In any case, how did you partition your drive?  Did you partition it right at the start before you initiated this guide or did you do it after.  If you did it after, which program did you use?

Hopefully you can provide some information about this.
Thanks in advance.</description>
		<content:encoded><![CDATA[<p>Thank you very much for this very nice guide.  Its great!!!</p>
<p>However whilst I am using Fedora 9, I got stuck at the command: drbdadm create-md r0<br />
My machine just didn&#8217;t recognise this command by giving the error message: &#8220;command not found&#8221;</p>
<p>Would you be able to shed some light on a reason why this may be happening?</p>
<p>I know I haven&#8217;t given much information about it but basically I followed your guide step by step and its perfect until the part where I need to enter: &#8220;drbdadm create-md r0&#8243;</p>
<p>Also, when I try to partition as per your guide, using gparted, the system doesn&#8217;t recognise the partitions in Fedora9 which is strange to me.  In any case, how did you partition your drive?  Did you partition it right at the start before you initiated this guide or did you do it after.  If you did it after, which program did you use?</p>
<p>Hopefully you can provide some information about this.<br />
Thanks in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew</title>
		<link>http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-160</link>
		<dc:creator>Matthew</dc:creator>
		<pubDate>Wed, 10 Dec 2008 21:47:39 +0000</pubDate>
		<guid isPermaLink="false">http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-160</guid>
		<description>Thank you very much.  This procedure was very easily modified for use under Ubuntu 8.04.  

The only additional thing I have is to alter the rc links so that the procs you are starting via heartbeat don't try to start by themselves at boot.</description>
		<content:encoded><![CDATA[<p>Thank you very much.  This procedure was very easily modified for use under Ubuntu 8.04.  </p>
<p>The only additional thing I have is to alter the rc links so that the procs you are starting via heartbeat don&#8217;t try to start by themselves at boot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis</title>
		<link>http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-150</link>
		<dc:creator>Dennis</dc:creator>
		<pubDate>Wed, 12 Nov 2008 16:54:10 +0000</pubDate>
		<guid isPermaLink="false">http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-150</guid>
		<description>You are the man!!
For some reason when reading posts about DRBD nobody says anything about filesystem and mount points. You where the first one I found
Great Job</description>
		<content:encoded><![CDATA[<p>You are the man!!<br />
For some reason when reading posts about DRBD nobody says anything about filesystem and mount points. You where the first one I found<br />
Great Job</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: douglas</title>
		<link>http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-149</link>
		<dc:creator>douglas</dc:creator>
		<pubDate>Mon, 10 Nov 2008 12:15:32 +0000</pubDate>
		<guid isPermaLink="false">http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-149</guid>
		<description>thankyou for this article. It's amazing.</description>
		<content:encoded><![CDATA[<p>thankyou for this article. It&#8217;s amazing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Linux Admin</title>
		<link>http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-143</link>
		<dc:creator>Linux Admin</dc:creator>
		<pubDate>Sun, 28 Sep 2008 15:14:19 +0000</pubDate>
		<guid isPermaLink="false">http://little.bluethings.net/2008/04/17/high-availability-with-fedora-drbd-heartbeat-and-mon/#comment-143</guid>
		<description>This was just what I was looking for to get my drbd setup on Fedora 9. I have to make some obvious adjustments because I used F9 and DRBD8.2.6 but it worked. Awesome!!</description>
		<content:encoded><![CDATA[<p>This was just what I was looking for to get my drbd setup on Fedora 9. I have to make some obvious adjustments because I used F9 and DRBD8.2.6 but it worked. Awesome!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
