<?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: redhat linux remove quorum device in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/redhat-linux-remove-quorum-device/m-p/4710486#M56792</link>
    <description>&amp;gt; removed the old quorum from cluster using cman_tool leave remove&lt;BR /&gt;&lt;BR /&gt;The command "cman_tool leave remove" does *not* remove the quorum device: when you run this command on a node, that *node* will attempt to leave the cluster. If you have cluster subsystems (like DLM or GFS) running at this point, the command will fail.&lt;BR /&gt;&lt;BR /&gt;I've seen this exact same misunderstanding once before on this forum: what made you think "cman_tool leave remove" was appropriate in this procedure? Perhaps there is an error in some commonly-used document.&lt;BR /&gt;&lt;BR /&gt;You don't have to stop cman to change the quorum device; if your cluster has no other problems, you can shutdown and restart the qdiskd service only. &lt;BR /&gt;&lt;BR /&gt;If you change the quorum device while the cluster is running, the old quorum device may remain listed in the clustat output (but please note that it's state will be "Offline"). Once the quorum device change is complete, you may have two quorum devices in the clustat output; this is a cosmetic problem only and should not affect the functionality of the cluster (or so RedHat's "RHEL 5.4 Storage and Clustering" course instructor told me).&lt;BR /&gt;&lt;BR /&gt;I think more information about the current state of your cluster and node is needed before I can suggest a fix for your problem.&lt;BR /&gt;&lt;BR /&gt;Please show the output of all these commands:&lt;BR /&gt;&lt;BR /&gt;service cman status&lt;BR /&gt;service clvmd status&lt;BR /&gt;service rgmanager status&lt;BR /&gt;service qdiskd status&lt;BR /&gt;service gfs status&lt;BR /&gt;service gfs2 status&lt;BR /&gt;cman_tool nodes&lt;BR /&gt;&lt;BR /&gt;If "service cman status" indicates cman is running, please show the output of "cman_tool services" too.&lt;BR /&gt;&lt;BR /&gt;Perhaps your earlier "cman_tool leave remove" caused cman to stop? In that case, run "service cman start". If that works correctly, verify that all the cluster services you need are running.&lt;BR /&gt;&lt;BR /&gt;MK</description>
    <pubDate>Thu, 02 Dec 2010 10:45:26 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2010-12-02T10:45:26Z</dc:date>
    <item>
      <title>redhat linux remove quorum device</title>
      <link>https://community.hpe.com/t5/operating-system-linux/redhat-linux-remove-quorum-device/m-p/4710484#M56790</link>
      <description>hi, I am using redhat linux 5.3 with  2 node cluster.Trying to remove existing quorum device and add new quorum coming from different SAN.&lt;BR /&gt;From existing threads posted here  I understood  that neither cluster nor server will be effected while performing this task.&lt;BR /&gt;&lt;BR /&gt;after stopping quorumd created new quorum device using mkqdisk command. removed the old quorum from cluster using cman_tool leave remove and ensured the quorum isnt member using cman_tool nodes command. But the clustat is still displaying this quorum as a member.&lt;BR /&gt;&lt;BR /&gt;after editing cluster.conf file with new quorum device tried to restart cman, but got below error. could someone assist me in resolving this issue. &lt;BR /&gt;&lt;BR /&gt;  Stopping cman... failed&lt;BR /&gt;/usr/sbin/cman_tool: Error leaving cluster: Device or resource busy&lt;BR /&gt;                                                           [FAILED]&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Nov 2010 12:24:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/redhat-linux-remove-quorum-device/m-p/4710484#M56790</guid>
      <dc:creator>B kiran</dc:creator>
      <dc:date>2010-11-08T12:24:12Z</dc:date>
    </item>
    <item>
      <title>Re: redhat linux remove quorum device</title>
      <link>https://community.hpe.com/t5/operating-system-linux/redhat-linux-remove-quorum-device/m-p/4710485#M56791</link>
      <description>Sounds like RH cluster not Serviceguard to me. Sorry, cannot help you here.</description>
      <pubDate>Thu, 02 Dec 2010 08:51:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/redhat-linux-remove-quorum-device/m-p/4710485#M56791</guid>
      <dc:creator>John Bigg</dc:creator>
      <dc:date>2010-12-02T08:51:07Z</dc:date>
    </item>
    <item>
      <title>Re: redhat linux remove quorum device</title>
      <link>https://community.hpe.com/t5/operating-system-linux/redhat-linux-remove-quorum-device/m-p/4710486#M56792</link>
      <description>&amp;gt; removed the old quorum from cluster using cman_tool leave remove&lt;BR /&gt;&lt;BR /&gt;The command "cman_tool leave remove" does *not* remove the quorum device: when you run this command on a node, that *node* will attempt to leave the cluster. If you have cluster subsystems (like DLM or GFS) running at this point, the command will fail.&lt;BR /&gt;&lt;BR /&gt;I've seen this exact same misunderstanding once before on this forum: what made you think "cman_tool leave remove" was appropriate in this procedure? Perhaps there is an error in some commonly-used document.&lt;BR /&gt;&lt;BR /&gt;You don't have to stop cman to change the quorum device; if your cluster has no other problems, you can shutdown and restart the qdiskd service only. &lt;BR /&gt;&lt;BR /&gt;If you change the quorum device while the cluster is running, the old quorum device may remain listed in the clustat output (but please note that it's state will be "Offline"). Once the quorum device change is complete, you may have two quorum devices in the clustat output; this is a cosmetic problem only and should not affect the functionality of the cluster (or so RedHat's "RHEL 5.4 Storage and Clustering" course instructor told me).&lt;BR /&gt;&lt;BR /&gt;I think more information about the current state of your cluster and node is needed before I can suggest a fix for your problem.&lt;BR /&gt;&lt;BR /&gt;Please show the output of all these commands:&lt;BR /&gt;&lt;BR /&gt;service cman status&lt;BR /&gt;service clvmd status&lt;BR /&gt;service rgmanager status&lt;BR /&gt;service qdiskd status&lt;BR /&gt;service gfs status&lt;BR /&gt;service gfs2 status&lt;BR /&gt;cman_tool nodes&lt;BR /&gt;&lt;BR /&gt;If "service cman status" indicates cman is running, please show the output of "cman_tool services" too.&lt;BR /&gt;&lt;BR /&gt;Perhaps your earlier "cman_tool leave remove" caused cman to stop? In that case, run "service cman start". If that works correctly, verify that all the cluster services you need are running.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Thu, 02 Dec 2010 10:45:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/redhat-linux-remove-quorum-device/m-p/4710486#M56792</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2010-12-02T10:45:26Z</dc:date>
    </item>
  </channel>
</rss>

