<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)">  <style>  </style>  </head> <body bgcolor=white lang=EN-US link=blue vlink=blue> <div class=Section1> What type of vmware environment? (VI ESX 3, Server, Workstation, or one of the older platforms?)<o:p></o:p> <o:p> </o:p> The Vmware forums have a fair amount of help on how to handle clock drift. Are you on AMD or Intel, 32 or 64 bit?<o:p></o:p> <o:p> </o:p> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> From: linux-cluster-bounces@redhat.com [mailto:linux-cluster-bounces@redhat.com] On Behalf Of Jeroen van den Horn Sent: Friday, March 30, 2007 10:07 AM To: linux clustering Subject: Re: [Linux-cluster] Fenced node never reboots properly<o:p></o:p> </div> <o:p> </o:p> In response to Lon's suggestion I modified the fence_vmware code and set the type of reset to HARD - cluster node now resets properly. Remaining issue is that under VMWare we are still experiencing performance issues. It's as if a node in the cluster starts 'lagging behind' (also the system clock starts drifting) and that after some time one of the nodes declares the other dead. Does anybody have any pointers towards performance issues and/or clock drifting with GFS on virtual machines? Regards, Jeroen <o:p></o:p> I'm using fence_vmware which I downloaded from some CVS repository. Good to hear that that is the issue - I'll take a look at the source and see whether the VMWare API support some sort of 'hard reset'. Jeroen Lon Hohberger wrote: <o:p></o:p> <pre wrap="">On Thu, Mar 29, 2007 at 10:04:00AM +0200, Jeroen van den Horn wrote:<o:p></o:p></pre><pre> <o:p></o:p></pre> <blockquote style='margin-top:5.0pt;margin-bottom:5.0pt' type=cite><pre wrap="">However during shutdown node 2 executes /etc/rc6.d/S31umountnfs (it's a <o:p></o:p></pre><pre>Debian system) which also attempts to unmount the GFS disk - result: <o:p></o:p></pre><pre>kernel OOPS. The system continues shutdown until it says 'Will now <o:p></o:p></pre><pre>restart.' but that's the end of it. I've tried setting the <o:p></o:p></pre><pre>/proc/sys/kernel/panic and added 'panic=5' to the kernel boot options <o:p></o:p></pre><pre>but to no avail.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>I'm really at a loss here - does anybody have any suggestions on how to <o:p></o:p></pre><pre>solve this problem?<o:p></o:p></pre><pre> <o:p></o:p></pre></blockquote> <pre wrap=""><o:p> </o:p></pre><pre>Yes, it's supposed to be killed (immediately) when fenced, not<o:p></o:p></pre><pre>gracefully attempting to shut down. What fencing agent are you using?<o:p></o:p></pre><pre>It sounds like there's a bug.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>-- Lon<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre> <o:p></o:p> <pre><o:p> </o:p></pre><pre style='text-align:center'> <hr size=4 width="90%" align=center> </pre><pre><o:p> </o:p></pre><pre>--<o:p></o:p></pre><pre>Linux-cluster mailing list<o:p></o:p></pre><pre><a href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a><o:p></o:p></pre><pre><a href="https://www.redhat.com/mailman/listinfo/linux-cluster">https://www.redhat.com/mailman/listinfo/linux-cluster</a><o:p></o:p></pre> <o:p> </o:p> </div> </body> </html>