<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: cluster lock disk in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk/m-p/3841794#M696293</link>
    <description>The cluster lock disc does not hav eto be activated to be useable. It MUST be activated at the time of creating teh cluster and writing the cluster lock bits to it, but from then on it does need to be activated.&lt;BR /&gt;If you have a dedicated CL disk and VG,not activated by any package, then this would be normal</description>
    <pubDate>Fri, 11 Aug 2006 05:20:31 GMT</pubDate>
    <dc:creator>melvyn burnard</dc:creator>
    <dc:date>2006-08-11T05:20:31Z</dc:date>
    <item>
      <title>cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk/m-p/3841793#M696292</link>
      <description>I am building a cluster and I decided to keep the cluster lock disk a 1GB disk alone created from EVA. this lock disk does not seem to be activated on whatever node, however when i remove the heartbeat, everything happens as expected. &lt;BR /&gt;Is it normal that the cluster lock disk will not be activated? I don't have any lv on it.&lt;BR /&gt;What do you advice?</description>
      <pubDate>Fri, 11 Aug 2006 05:18:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk/m-p/3841793#M696292</guid>
      <dc:creator>simon_164</dc:creator>
      <dc:date>2006-08-11T05:18:23Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk/m-p/3841794#M696293</link>
      <description>The cluster lock disc does not hav eto be activated to be useable. It MUST be activated at the time of creating teh cluster and writing the cluster lock bits to it, but from then on it does need to be activated.&lt;BR /&gt;If you have a dedicated CL disk and VG,not activated by any package, then this would be normal</description>
      <pubDate>Fri, 11 Aug 2006 05:20:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk/m-p/3841794#M696293</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2006-08-11T05:20:31Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk/m-p/3841795#M696294</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;This points to a few possible issues:&lt;BR /&gt;&lt;BR /&gt;1) The cluster lock disk does not get "activated" When heartbeat is lost both nodes attempt to establish a lock on it. The first node achieves it, the one second one if it tries should fail and TOC, wish is a reboot with a crash dump.&lt;BR /&gt;&lt;BR /&gt;2) There will be no noticable disk activity on the cluster lock disk when a cluster uses it so dont look for a flashing green light.&lt;BR /&gt;&lt;BR /&gt;3) The possible problem maybe a prolbem the the configuration on both nodes not being consistent, the binary configuration files being different or perhaps you have two heartbeats and disrupting one does not trigger any cluster change.&lt;BR /&gt;&lt;BR /&gt;You need to look at /var/adm/syslog/syslog.log on both systems when testing and that will provide you some clue as to what is happening.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Fri, 11 Aug 2006 05:24:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk/m-p/3841795#M696294</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-08-11T05:24:03Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk/m-p/3841796#M696295</link>
      <description>steven: this is what is happening, while testing -- one node TOCed and the other worked fine. which is what is expected. but i was asking since I am making a cluster lock disk alone. By the way how would i know if the lock bit is created on the disk? any command?</description>
      <pubDate>Fri, 11 Aug 2006 05:26:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk/m-p/3841796#M696295</guid>
      <dc:creator>simon_164</dc:creator>
      <dc:date>2006-08-11T05:26:56Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk/m-p/3841797#M696296</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Very iteresting. I've never checked that.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B9903-90035/B9903-90035.pdf" target="_blank"&gt;http://docs.hp.com/en/B9903-90035/B9903-90035.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Its a linux doc but it has a reference to the cluster lock disk and bit, and may contain the command you seek.&lt;BR /&gt;&lt;BR /&gt;The way I tell the cluster lock disk has been activated is the second node going TOC on me.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Fri, 11 Aug 2006 05:47:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk/m-p/3841797#M696296</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-08-11T05:47:53Z</dc:date>
    </item>
    <item>
      <title>Re: cluster lock disk</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk/m-p/3841798#M696297</link>
      <description>&amp;gt;By the way how would i know if the lock bit is created on the disk? any command?&lt;BR /&gt;&lt;BR /&gt;Not easy!&lt;BR /&gt;This is written in the Bad Block Relocation area of the disk (hence the reason you cannot mirror this bit).&lt;BR /&gt;When you start your cluster running, it polls teh configured disc from each node at start time an dthen every 60 minutes.&lt;BR /&gt;If the bit were NOT set, it would log the cluster lock disc as unavailable in syslog.log.&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Aug 2006 06:17:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cluster-lock-disk/m-p/3841798#M696297</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2006-08-11T06:17:12Z</dc:date>
    </item>
  </channel>
</rss>

