<?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: mounting disk cluster wide in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/mounting-disk-cluster-wide/m-p/5274341#M101262</link>
    <description>$ HELP MOUNT /SYSTEM&lt;BR /&gt;$ HELP MOUNT /CLUSTER&lt;BR /&gt;&lt;BR /&gt;You will want to use a derivative of the MSCPMOUNT.COM template, as that deals with the other case here, which is what happens to your disks when nodes depart and arrive.&lt;BR /&gt;&lt;BR /&gt;See the System Manager's Manual Essentials in the documentation set:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.hp.com/go/openvms/doc" target="_blank"&gt;http://www.hp.com/go/openvms/doc&lt;/A&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 18 Feb 2011 16:55:23 GMT</pubDate>
    <dc:creator>Hoff</dc:creator>
    <dc:date>2011-02-18T16:55:23Z</dc:date>
    <item>
      <title>mounting disk cluster wide</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mounting-disk-cluster-wide/m-p/5274340#M101261</link>
      <description>are these two the same&lt;BR /&gt;&lt;BR /&gt;from one node,&lt;BR /&gt;$mount/cluster {disk} {label}&lt;BR /&gt;&lt;BR /&gt;from all node,&lt;BR /&gt;$mount/system {disk} {label}&lt;BR /&gt;&lt;BR /&gt;Scotty</description>
      <pubDate>Fri, 18 Feb 2011 16:44:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mounting-disk-cluster-wide/m-p/5274340#M101261</guid>
      <dc:creator>Scotty HD</dc:creator>
      <dc:date>2011-02-18T16:44:54Z</dc:date>
    </item>
    <item>
      <title>Re: mounting disk cluster wide</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mounting-disk-cluster-wide/m-p/5274341#M101262</link>
      <description>$ HELP MOUNT /SYSTEM&lt;BR /&gt;$ HELP MOUNT /CLUSTER&lt;BR /&gt;&lt;BR /&gt;You will want to use a derivative of the MSCPMOUNT.COM template, as that deals with the other case here, which is what happens to your disks when nodes depart and arrive.&lt;BR /&gt;&lt;BR /&gt;See the System Manager's Manual Essentials in the documentation set:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.hp.com/go/openvms/doc" target="_blank"&gt;http://www.hp.com/go/openvms/doc&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Feb 2011 16:55:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mounting-disk-cluster-wide/m-p/5274341#M101262</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2011-02-18T16:55:23Z</dc:date>
    </item>
    <item>
      <title>Re: mounting disk cluster wide</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mounting-disk-cluster-wide/m-p/5274342#M101263</link>
      <description>Scotty,&lt;BR /&gt;&lt;BR /&gt;  They may be the same, but it depends on your disk configuration, and the order that nodes are booted.&lt;BR /&gt;&lt;BR /&gt; For example, in a SAN environment where every node can see every disk independently, mounting on each node makes some sense. However, if some disks are local to a particular node, then boot order matters. &lt;BR /&gt;&lt;BR /&gt;Consider nodes A and B. If A boots before B, A cannot see B's local disks and therefore cannot mount them. If B only mounts the disks to itself, then how will they be mounted on A?&lt;BR /&gt;&lt;BR /&gt;  My preference is to use MOUNT/CLUSTER on each node. Mount logic is to check that an expected disk exists:&lt;BR /&gt;&lt;BR /&gt;F$GETDVI(disk,"EXISTS")&lt;BR /&gt;&lt;BR /&gt;if it does check if its mounted&lt;BR /&gt;&lt;BR /&gt;F$GETDVI(disk,"MNT")&lt;BR /&gt;&lt;BR /&gt;if not, mount it /CLUSTER.&lt;BR /&gt;&lt;BR /&gt;If you do this on each node, you can expect a consistent set of disks are mounted after booting nodes in any order.&lt;BR /&gt;&lt;BR /&gt;I also recommend a single, clusterwide shared MOUNT procedure. That way you're guaranteed every node expects and mounts the same set of disks.</description>
      <pubDate>Fri, 18 Feb 2011 21:40:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mounting-disk-cluster-wide/m-p/5274342#M101263</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2011-02-18T21:40:30Z</dc:date>
    </item>
    <item>
      <title>Re: mounting disk cluster wide</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mounting-disk-cluster-wide/m-p/5274343#M101264</link>
      <description>Hoff#&lt;BR /&gt;John Gillings#&lt;BR /&gt;thanks for reply.&lt;BR /&gt;&lt;BR /&gt;i will keep John's comments in mind when i do implementation.&lt;BR /&gt;&lt;BR /&gt;my question is in a way answered that,&lt;BR /&gt;lets say cluster has two nodes, A ,B. both are up.&lt;BR /&gt;the above two commands would make the disk cluster available and&lt;BR /&gt;get synchornized for cluster wide access in the same way.&lt;BR /&gt;&lt;BR /&gt;Scotty</description>
      <pubDate>Sat, 19 Feb 2011 02:48:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mounting-disk-cluster-wide/m-p/5274343#M101264</guid>
      <dc:creator>Scotty HD</dc:creator>
      <dc:date>2011-02-19T02:48:10Z</dc:date>
    </item>
    <item>
      <title>Re: mounting disk cluster wide</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mounting-disk-cluster-wide/m-p/5274344#M101265</link>
      <description>Scotty,&lt;BR /&gt;&lt;BR /&gt;  If both systems are booted into the cluster, and the disk in question is visible from both nodes, then:&lt;BR /&gt;&lt;BR /&gt;$ MOUNT/CLUSTER&lt;BR /&gt;&lt;BR /&gt;on either node will mount the disk on all nodes in the cluster. It's equivalent to executing the same:&lt;BR /&gt;&lt;BR /&gt;$ MOUNT/SYSTEM &lt;BR /&gt;&lt;BR /&gt;command on each node in the cluster.&lt;BR /&gt;&lt;BR /&gt;The tricky part is dealing with all the combinations and permutations of nodes booting in different orders. It's greatly simplified with SAN storage, as you don't need to worry about visibibiliy of served disks.</description>
      <pubDate>Sat, 19 Feb 2011 03:08:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mounting-disk-cluster-wide/m-p/5274344#M101265</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2011-02-19T03:08:23Z</dc:date>
    </item>
    <item>
      <title>Re: mounting disk cluster wide</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mounting-disk-cluster-wide/m-p/5274345#M101266</link>
      <description>thanks to all for help.&lt;BR /&gt;&lt;BR /&gt;Scotty</description>
      <pubDate>Sat, 19 Feb 2011 03:55:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mounting-disk-cluster-wide/m-p/5274345#M101266</guid>
      <dc:creator>Scotty HD</dc:creator>
      <dc:date>2011-02-19T03:55:15Z</dc:date>
    </item>
    <item>
      <title>Re: mounting disk cluster wide</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mounting-disk-cluster-wide/m-p/5274346#M101267</link>
      <description>thanks a lot&lt;BR /&gt;&lt;BR /&gt;Scotty</description>
      <pubDate>Sat, 19 Feb 2011 03:56:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mounting-disk-cluster-wide/m-p/5274346#M101267</guid>
      <dc:creator>Scotty HD</dc:creator>
      <dc:date>2011-02-19T03:56:00Z</dc:date>
    </item>
  </channel>
</rss>

