<?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: PV-TIMEOUT in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/pv-timeout/m-p/4765778#M549170</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;PVRA stores the structural information like size and identification of the P.V. There are around 19 commands backed up by vgcfgbackup by the LVM subsystem and one of them is pvchange and hence as timeout is configured with pvchange -t, it would maintain that info in the file /etc/lvmconf/vgname.conf.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Ismail Azad</description>
    <pubDate>Wed, 16 Mar 2011 05:16:38 GMT</pubDate>
    <dc:creator>Ismail Azad</dc:creator>
    <dc:date>2011-03-16T05:16:38Z</dc:date>
    <item>
      <title>PV-TIMEOUT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pv-timeout/m-p/4765777#M549169</link>
      <description>1. Can any tell me where store the PV-TIMEOUT value of a PV? Is it store in the PVRA in the disk or in the systems /etc/lvmconf/vgxy.conf file?&lt;BR /&gt;&lt;BR /&gt;2. If i change PV-TIMEOUT value in the primary node,then it is necessary to change the same in the 2nd node in a cluster?</description>
      <pubDate>Wed, 16 Mar 2011 05:11:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pv-timeout/m-p/4765777#M549169</guid>
      <dc:creator>Abhijit.A</dc:creator>
      <dc:date>2011-03-16T05:11:32Z</dc:date>
    </item>
    <item>
      <title>Re: PV-TIMEOUT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pv-timeout/m-p/4765778#M549170</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;PVRA stores the structural information like size and identification of the P.V. There are around 19 commands backed up by vgcfgbackup by the LVM subsystem and one of them is pvchange and hence as timeout is configured with pvchange -t, it would maintain that info in the file /etc/lvmconf/vgname.conf.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Ismail Azad</description>
      <pubDate>Wed, 16 Mar 2011 05:16:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pv-timeout/m-p/4765778#M549170</guid>
      <dc:creator>Ismail Azad</dc:creator>
      <dc:date>2011-03-16T05:16:38Z</dc:date>
    </item>
    <item>
      <title>Re: PV-TIMEOUT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pv-timeout/m-p/4765779#M549171</link>
      <description>Thanks for replying Ismail.&lt;BR /&gt;&lt;BR /&gt;So if we change PV-TIMEOUT in primary node then we have to change the same in 2nd node also in cluster.</description>
      <pubDate>Wed, 16 Mar 2011 05:48:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pv-timeout/m-p/4765779#M549171</guid>
      <dc:creator>Abhijit.A</dc:creator>
      <dc:date>2011-03-16T05:48:52Z</dc:date>
    </item>
    <item>
      <title>Re: PV-TIMEOUT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pv-timeout/m-p/4765780#M549172</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Since on SG , cluster architecture is normally of the shared disk type, I would say yup!.&lt;BR /&gt;&lt;BR /&gt;Welcome to ITRC! Don't forget to assign points.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Ismail Azad</description>
      <pubDate>Wed, 16 Mar 2011 06:44:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pv-timeout/m-p/4765780#M549172</guid>
      <dc:creator>Ismail Azad</dc:creator>
      <dc:date>2011-03-16T06:44:12Z</dc:date>
    </item>
    <item>
      <title>Re: PV-TIMEOUT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pv-timeout/m-p/4765781#M549173</link>
      <description>required information what happens same thing in SG environment.</description>
      <pubDate>Mon, 21 Mar 2011 06:00:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pv-timeout/m-p/4765781#M549173</guid>
      <dc:creator>Abhijit.A</dc:creator>
      <dc:date>2011-03-21T06:00:23Z</dc:date>
    </item>
    <item>
      <title>Re: PV-TIMEOUT</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pv-timeout/m-p/4765782#M549174</link>
      <description>On SG environment, certain changes made in LVM, needs to be aware by all nodes within the cluster.&lt;BR /&gt;&lt;BR /&gt;Rgds...</description>
      <pubDate>Mon, 21 Mar 2011 06:48:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pv-timeout/m-p/4765782#M549174</guid>
      <dc:creator>P Arumugavel</dc:creator>
      <dc:date>2011-03-21T06:48:26Z</dc:date>
    </item>
  </channel>
</rss>

