<?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: slvmvg file in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/slvmvg-file/m-p/2876995#M636255</link>
    <description>Hi, Randy!&lt;BR /&gt;&lt;BR /&gt;The cmlvmd needs this device file to initialize the SLVM during cluster start. I.e. the LVM_START_SLVM ioctl() takes the opened file as an argument. /dev/slvmvg usually points to the root VG (64, 0x0).&lt;BR /&gt;&lt;BR /&gt;BTW, vgscan is known to have problems with it. Fixed with recent LVM commands patches.&lt;BR /&gt;&lt;BR /&gt;Best regards...&lt;BR /&gt; Dietmar.</description>
    <pubDate>Wed, 08 Jan 2003 14:25:20 GMT</pubDate>
    <dc:creator>Dietmar Konermann</dc:creator>
    <dc:date>2003-01-08T14:25:20Z</dc:date>
    <item>
      <title>slvmvg file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/slvmvg-file/m-p/2876994#M636254</link>
      <description>Why is the slvvmg device file created in a service guard environment?</description>
      <pubDate>Wed, 08 Jan 2003 14:10:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/slvmvg-file/m-p/2876994#M636254</guid>
      <dc:creator>randy lee</dc:creator>
      <dc:date>2003-01-08T14:10:11Z</dc:date>
    </item>
    <item>
      <title>Re: slvmvg file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/slvmvg-file/m-p/2876995#M636255</link>
      <description>Hi, Randy!&lt;BR /&gt;&lt;BR /&gt;The cmlvmd needs this device file to initialize the SLVM during cluster start. I.e. the LVM_START_SLVM ioctl() takes the opened file as an argument. /dev/slvmvg usually points to the root VG (64, 0x0).&lt;BR /&gt;&lt;BR /&gt;BTW, vgscan is known to have problems with it. Fixed with recent LVM commands patches.&lt;BR /&gt;&lt;BR /&gt;Best regards...&lt;BR /&gt; Dietmar.</description>
      <pubDate>Wed, 08 Jan 2003 14:25:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/slvmvg-file/m-p/2876995#M636255</guid>
      <dc:creator>Dietmar Konermann</dc:creator>
      <dc:date>2003-01-08T14:25:20Z</dc:date>
    </item>
    <item>
      <title>Re: slvmvg file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/slvmvg-file/m-p/2876996#M636256</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;It's used only by cmlvmd daemon ... for shared vg and from the documentation :&lt;BR /&gt;&lt;BR /&gt;Cluster Logical Volume Manager Daemon: cmlvmd&lt;BR /&gt;This daemon is responsible for keeping track of all the volume group(s) that have been made cluster aware. When a volume group is made&lt;BR /&gt;cluster aware, a cluster node can only activate it in exclusive mode. This prevents the volume group from being activated in write mode by more than one node at a time.&lt;BR /&gt;&lt;BR /&gt;Regards.</description>
      <pubDate>Wed, 08 Jan 2003 14:30:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/slvmvg-file/m-p/2876996#M636256</guid>
      <dc:creator>Jean-Louis Phelix</dc:creator>
      <dc:date>2003-01-08T14:30:52Z</dc:date>
    </item>
  </channel>
</rss>

