<?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: vgchange -c y in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vgchange-c-y/m-p/5284139#M534585</link>
    <description>If a VG is clustered (i.e. the disks have been presented to two or more hosts) then yes, "vgchange -c y" is necessary. &lt;BR /&gt;&lt;BR /&gt;Otherwise, the system will not enforce proper locking and there is a possibility of accidentally activating the VG and mounting the disk on more than one server simultaneously. This will cause data corruption, because of disk caching.&lt;BR /&gt;&lt;BR /&gt;When "vgchange -c y" is in effect on a VG, that VG cannot be activated with the usual "vgchange -a y": you must use "vgchange -a e" instead. And "vgchange -a e" works only when the server is running Serviceguard and a member of the cluster (the server status is "up" in "cmviewcl" output), AND no other node in the cluster has the same VG active.&lt;BR /&gt;&lt;BR /&gt;If the VG's disks are presented to one host only, then "vgchange -c y" is not necessary for that VG, even if the system is running Serviceguard. Normally, vg00 should *never* be in "vgchange -c y" mode.&lt;BR /&gt;&lt;BR /&gt;MK</description>
    <pubDate>Tue, 07 Jun 2011 13:10:34 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2011-06-07T13:10:34Z</dc:date>
    <item>
      <title>vgchange -c y</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgchange-c-y/m-p/5284138#M534584</link>
      <description>Hello,&lt;BR /&gt;I have two servers in a MCSG cluster.&lt;BR /&gt;after one year, MCSG is deactived the vg's are actived with vgchange -c n and vgchange -a y.&lt;BR /&gt;Now, i want  reactive the cluster.&lt;BR /&gt;Must i do a vgchange -c y before or not....&lt;BR /&gt;Thank's</description>
      <pubDate>Tue, 07 Jun 2011 12:21:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgchange-c-y/m-p/5284138#M534584</guid>
      <dc:creator>D.Blond</dc:creator>
      <dc:date>2011-06-07T12:21:27Z</dc:date>
    </item>
    <item>
      <title>Re: vgchange -c y</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgchange-c-y/m-p/5284139#M534585</link>
      <description>If a VG is clustered (i.e. the disks have been presented to two or more hosts) then yes, "vgchange -c y" is necessary. &lt;BR /&gt;&lt;BR /&gt;Otherwise, the system will not enforce proper locking and there is a possibility of accidentally activating the VG and mounting the disk on more than one server simultaneously. This will cause data corruption, because of disk caching.&lt;BR /&gt;&lt;BR /&gt;When "vgchange -c y" is in effect on a VG, that VG cannot be activated with the usual "vgchange -a y": you must use "vgchange -a e" instead. And "vgchange -a e" works only when the server is running Serviceguard and a member of the cluster (the server status is "up" in "cmviewcl" output), AND no other node in the cluster has the same VG active.&lt;BR /&gt;&lt;BR /&gt;If the VG's disks are presented to one host only, then "vgchange -c y" is not necessary for that VG, even if the system is running Serviceguard. Normally, vg00 should *never* be in "vgchange -c y" mode.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Tue, 07 Jun 2011 13:10:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgchange-c-y/m-p/5284139#M534585</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2011-06-07T13:10:34Z</dc:date>
    </item>
    <item>
      <title>Re: vgchange -c y</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgchange-c-y/m-p/5284140#M534586</link>
      <description>vgchange -a n  (volume group active no)&lt;BR /&gt;vgchange -a y (volume group active yes)&lt;BR /&gt;vgchange -s y (volume group sharing yes)&lt;BR /&gt;vgchange -s n(volume group sharing no)&lt;BR /&gt;vgchange -c y(clustering yes)&lt;BR /&gt;&lt;BR /&gt;This way u can easily remember&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;from u above postings u activated only volume group u have to activate cluster also&lt;BR /&gt;by using vgchange -c y&lt;BR /&gt;&lt;BR /&gt;thanks and regards&lt;BR /&gt;&lt;BR /&gt;Sajjad sahir</description>
      <pubDate>Wed, 15 Jun 2011 11:53:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgchange-c-y/m-p/5284140#M534586</guid>
      <dc:creator>Sajjad Sahir</dc:creator>
      <dc:date>2011-06-15T11:53:21Z</dc:date>
    </item>
    <item>
      <title>Re: vgchange -c y</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgchange-c-y/m-p/5284141#M534587</link>
      <description>thank's</description>
      <pubDate>Wed, 15 Jun 2011 12:30:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgchange-c-y/m-p/5284141#M534587</guid>
      <dc:creator>D.Blond</dc:creator>
      <dc:date>2011-06-15T12:30:41Z</dc:date>
    </item>
  </channel>
</rss>

