<?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: Activating VG in another cluster node in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055583#M600735</link>
    <description>what i remember is , we split in RW mode and and then vgchange -a y(whihc means "-c n" priorly)</description>
    <pubDate>Mon, 27 Aug 2007 22:04:40 GMT</pubDate>
    <dc:creator>skt_skt</dc:creator>
    <dc:date>2007-08-27T22:04:40Z</dc:date>
    <item>
      <title>Activating VG in another cluster node</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055574#M600726</link>
      <description>Thought I knew LVM well :-)&lt;BR /&gt;&lt;BR /&gt;I am having this strange problem while trying to active the replicated VG on an another cluster.&lt;BR /&gt;&lt;BR /&gt;1) Did a pairsplit and pairdisplay to make sure the CA pairs are in split mode&lt;BR /&gt;&lt;BR /&gt;2) VGimported the VG using the CA-SVOLS&lt;BR /&gt;&lt;BR /&gt;3) # vgchange -c n vgXX&lt;BR /&gt;Performed Configuration change.&lt;BR /&gt;Volume group "vgXX" has been successfully changed.&lt;BR /&gt;&lt;BR /&gt;   This will remove the cluster ID of the old cluster&lt;BR /&gt;&lt;BR /&gt;4) # vgchange -c y vgXX&lt;BR /&gt;Performed Configuration change.&lt;BR /&gt;Volume group "vgXX" has been successfully changed.&lt;BR /&gt;#&lt;BR /&gt;&lt;BR /&gt;   This will install the cluster ID of the new cluster (or that is what I thought :-))&lt;BR /&gt;&lt;BR /&gt;5)# vgchange -a e vgXX&lt;BR /&gt;vgchange: Volume group "/dev/vgXX" belongs to a different Cluster.  Activation failed.&lt;BR /&gt;&lt;BR /&gt;  I am also looking in to the possiblity of a LVM patch fix. But any thoughts ?&lt;BR /&gt;&lt;BR /&gt;Sundar.</description>
      <pubDate>Thu, 16 Aug 2007 11:58:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055574#M600726</guid>
      <dc:creator>Sundar_7</dc:creator>
      <dc:date>2007-08-16T11:58:16Z</dc:date>
    </item>
    <item>
      <title>Re: Activating VG in another cluster node</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055575#M600727</link>
      <description>When doing this, I always run vgchgid and I don't see that step.</description>
      <pubDate>Thu, 16 Aug 2007 12:08:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055575#M600727</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2007-08-16T12:08:56Z</dc:date>
    </item>
    <item>
      <title>Re: Activating VG in another cluster node</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055576#M600728</link>
      <description>Per my understanding, you dont need vgchgid if the system doesn't see both the PVOL and the SVOLs.&lt;BR /&gt;&lt;BR /&gt;The system is zoned to see only SVOLS and thus wont get "confused" seeing two disks with the same PVID/VGID.&lt;BR /&gt;&lt;BR /&gt;I know it doesn't hurt to try but the above sequence of commands should work.</description>
      <pubDate>Thu, 16 Aug 2007 12:17:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055576#M600728</guid>
      <dc:creator>Sundar_7</dc:creator>
      <dc:date>2007-08-16T12:17:55Z</dc:date>
    </item>
    <item>
      <title>Re: Activating VG in another cluster node</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055577#M600729</link>
      <description>The man page for vgchanges also indicates that you must run vgchange -a n before doing a -c y or -c n and obviously you didn't do that (nor could you). I think the vgchgid will actually take care of two problems at once.</description>
      <pubDate>Thu, 16 Aug 2007 12:29:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055577#M600729</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2007-08-16T12:29:01Z</dc:date>
    </item>
    <item>
      <title>Re: Activating VG in another cluster node</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055578#M600730</link>
      <description>Hi &lt;BR /&gt;&lt;BR /&gt;Suppose that you want to activate vg01 from nodeA to nodeB in your cluster (In normal case, this do by using MC/SG command).&lt;BR /&gt;I have done this job lots of time :)&lt;BR /&gt;&lt;BR /&gt;1) nodeA#umount all of mount point belong to vg01&lt;BR /&gt;2) nodeA#vgchange -a n vg01&lt;BR /&gt;3) nodeA#vgchange -c n vg01&lt;BR /&gt;4) nodeB#vgchange -c y vg01&lt;BR /&gt;5) nodeB#vgchange -a y vg01&lt;BR /&gt;&lt;BR /&gt;Hope this works :)&lt;BR /&gt;</description>
      <pubDate>Thu, 16 Aug 2007 20:43:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055578#M600730</guid>
      <dc:creator>Hoang Chi Cong_1</dc:creator>
      <dc:date>2007-08-16T20:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: Activating VG in another cluster node</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055579#M600731</link>
      <description>Hi,&lt;BR /&gt;You can do this:&lt;BR /&gt;&lt;BR /&gt;1. fuser -ku /dev/vgash/lvol1&lt;BR /&gt;2. umount /test &lt;BR /&gt;3. vgchange -a n vgash&lt;BR /&gt;4. vgchange -c n vgash&lt;BR /&gt;5. vgchange -a n vgash&lt;BR /&gt;6. vgchange -a y vgash&lt;BR /&gt;7. fsck -F vxfs /dev/vgash/lvol1&lt;BR /&gt;8. mount /dev/vgash/lvol1 /test&lt;BR /&gt;&lt;BR /&gt;Thanks &amp;amp; Regards&lt;BR /&gt;&lt;BR /&gt;A. Aashique</description>
      <pubDate>Fri, 17 Aug 2007 15:19:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055579#M600731</guid>
      <dc:creator>Aashique</dc:creator>
      <dc:date>2007-08-17T15:19:27Z</dc:date>
    </item>
    <item>
      <title>Re: Activating VG in another cluster node</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055580#M600732</link>
      <description>It turns out pairsplit does a read-only split of the SVOLS by default.&lt;BR /&gt;&lt;BR /&gt;So, the vgchange commands, though seem to complete successfully, is misleading.&lt;BR /&gt;&lt;BR /&gt;After splitting the pairs with -rw option, I was able to change the cluster ID and activate the VG in exclusive mode !&lt;BR /&gt;&lt;BR /&gt;HP LVM team ?!?!?!!!</description>
      <pubDate>Wed, 22 Aug 2007 12:35:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055580#M600732</guid>
      <dc:creator>Sundar_7</dc:creator>
      <dc:date>2007-08-22T12:35:47Z</dc:date>
    </item>
    <item>
      <title>Re: Activating VG in another cluster node</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055581#M600733</link>
      <description>CA split is RO only by default(but the BC split is RW by default).&lt;BR /&gt;&lt;BR /&gt;I used to mount the CA copy for backup; But never faced this problem as i always bring them up in normal(-a y) for backup.</description>
      <pubDate>Wed, 22 Aug 2007 22:17:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055581#M600733</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2007-08-22T22:17:06Z</dc:date>
    </item>
    <item>
      <title>Re: Activating VG in another cluster node</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055582#M600734</link>
      <description>Santhosh,&lt;BR /&gt;&lt;BR /&gt;   You will not be able to do a vgchange -a y if the source VG was part of a cluster.&lt;BR /&gt;&lt;BR /&gt;   In my opinion, vgchange -c y and -c n are very misleading. Had they complained that the configuration change cannot be performed due to read-only volumes, I would have figured instantly that the S-VOL was split read-only.&lt;BR /&gt;&lt;BR /&gt;Sundar.</description>
      <pubDate>Mon, 27 Aug 2007 15:55:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055582#M600734</guid>
      <dc:creator>Sundar_7</dc:creator>
      <dc:date>2007-08-27T15:55:35Z</dc:date>
    </item>
    <item>
      <title>Re: Activating VG in another cluster node</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055583#M600735</link>
      <description>what i remember is , we split in RW mode and and then vgchange -a y(whihc means "-c n" priorly)</description>
      <pubDate>Mon, 27 Aug 2007 22:04:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/activating-vg-in-another-cluster-node/m-p/4055583#M600735</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2007-08-27T22:04:40Z</dc:date>
    </item>
  </channel>
</rss>

