<?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: Volume Group read-only mode in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-read-only-mode/m-p/2501998#M655062</link>
    <description>just to make sure that you're aware of this...&lt;BR /&gt;With MC/SG, &lt;BR /&gt;pkg01 &lt;BR /&gt;on nodeA (ie vg01 "-a e") AND &lt;BR /&gt;on nodeB same vg01 "-a r" &lt;BR /&gt;&lt;BR /&gt;will give you problems if nodeA fails &lt;BR /&gt;as SG cannot start pkg01 on nodeB as long as it is read-only-activated (ie needs a "-a n" first).&lt;BR /&gt;&lt;BR /&gt;So as "-a r" is a kind of "jumping on thin ice" I always try to keep this time to a minimum level.&lt;BR /&gt;&lt;BR /&gt;take care, thomas.</description>
    <pubDate>Thu, 08 Mar 2001 09:26:20 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2001-03-08T09:26:20Z</dc:date>
    <item>
      <title>Volume Group read-only mode</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-read-only-mode/m-p/2501995#M655059</link>
      <description>We have cluster with two nodes.&lt;BR /&gt;VG has been activated  with vgchange -a y from node1 and with vgchange -a r  (read-only mode) from node2. Changes made from node1 since that  to files in file system residing in this VG are not  effective (or just visible?) from node2.&lt;BR /&gt;Is it right? Or the problem is in absence of some patches?</description>
      <pubDate>Wed, 07 Mar 2001 09:04:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-read-only-mode/m-p/2501995#M655059</guid>
      <dc:creator>Ivan Efimenko</dc:creator>
      <dc:date>2001-03-07T09:04:20Z</dc:date>
    </item>
    <item>
      <title>Re: Volume Group read-only mode</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-read-only-mode/m-p/2501996#M655060</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;When you work with Cluster you use the vgchange -a e, not -a y.&lt;BR /&gt;-a e option is exclusive mode.&lt;BR /&gt;&lt;BR /&gt;Work?s with the VG activate in two machines&lt;BR /&gt;is only possible with the LockManager Software,&lt;BR /&gt;this software work?s with MC/ServiceGuard.&lt;BR /&gt;&lt;BR /&gt;When you active the volume goup, is write in VGSA, and if other machi try to activate the volume group the "Conflicts Mode Activate" is reposted.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 07 Mar 2001 15:02:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-read-only-mode/m-p/2501996#M655060</guid>
      <dc:creator>Andre Machado_1</dc:creator>
      <dc:date>2001-03-07T15:02:22Z</dc:date>
    </item>
    <item>
      <title>Re: Volume Group read-only mode</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-read-only-mode/m-p/2501997#M655061</link>
      <description>&lt;BR /&gt;The problem is that the file system structures are read at mount time.  SO if you add a file to the filesystem from the read/write side the read only side does not see it. &lt;BR /&gt;&lt;BR /&gt;Read only activation was not meant for this.  You should have 2 different logical volumes 1 being used Read/write on the node that has the volume group vgchange -a y.  Another logical volume mounted read only from the system that has the volume group vgchange -a r&lt;BR /&gt;&lt;BR /&gt;Many people use this as a way to split a mirrored logical volume and mount the split off copy read only on another system so it can be backed up.  &lt;BR /&gt;&lt;BR /&gt;If you want another system to see a filesystem use NFS.&lt;BR /&gt;&lt;BR /&gt;I hope this clears up some of the vgchange -a r questions.</description>
      <pubDate>Wed, 07 Mar 2001 15:24:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-read-only-mode/m-p/2501997#M655061</guid>
      <dc:creator>Emil Velez</dc:creator>
      <dc:date>2001-03-07T15:24:35Z</dc:date>
    </item>
    <item>
      <title>Re: Volume Group read-only mode</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-read-only-mode/m-p/2501998#M655062</link>
      <description>just to make sure that you're aware of this...&lt;BR /&gt;With MC/SG, &lt;BR /&gt;pkg01 &lt;BR /&gt;on nodeA (ie vg01 "-a e") AND &lt;BR /&gt;on nodeB same vg01 "-a r" &lt;BR /&gt;&lt;BR /&gt;will give you problems if nodeA fails &lt;BR /&gt;as SG cannot start pkg01 on nodeB as long as it is read-only-activated (ie needs a "-a n" first).&lt;BR /&gt;&lt;BR /&gt;So as "-a r" is a kind of "jumping on thin ice" I always try to keep this time to a minimum level.&lt;BR /&gt;&lt;BR /&gt;take care, thomas.</description>
      <pubDate>Thu, 08 Mar 2001 09:26:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/volume-group-read-only-mode/m-p/2501998#M655062</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2001-03-08T09:26:20Z</dc:date>
    </item>
  </channel>
</rss>

