<?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: Mount timeout in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967261#M75009</link>
    <description>Thanx for all your suggestions. I think the best way is to use /NOASSSIST with the mount command.&lt;BR /&gt;&lt;BR /&gt;Vladky</description>
    <pubDate>Wed, 15 Mar 2006 04:43:01 GMT</pubDate>
    <dc:creator>vladky</dc:creator>
    <dc:date>2006-03-15T04:43:01Z</dc:date>
    <item>
      <title>Mount timeout</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967255#M75003</link>
      <description>Hi everybody, I would like to change the timeout during a disk mount operation, if the disk is not mountable. Is it possible to modify this through some sysgen paramater ?</description>
      <pubDate>Wed, 15 Mar 2006 03:04:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967255#M75003</guid>
      <dc:creator>vladky</dc:creator>
      <dc:date>2006-03-15T03:04:33Z</dc:date>
    </item>
    <item>
      <title>Re: Mount timeout</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967256#M75004</link>
      <description>Vladky,&lt;BR /&gt;&lt;BR /&gt;the timeouts involved during a disk mount are most likely not changeable, as they are hidden in the underlying disk/port drivers.&lt;BR /&gt;&lt;BR /&gt;What problem are you trying to solve ?&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Wed, 15 Mar 2006 03:19:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967256#M75004</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2006-03-15T03:19:05Z</dc:date>
    </item>
    <item>
      <title>Re: Mount timeout</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967257#M75005</link>
      <description>Hi, thanx for your answer. Last time I had problem by system boot. One disk device became unmountable (some HW problem) and the startup procedure was waiting and trying to mount this device. I was not able to skip this mounting operation and I had to abort the boot process. Then I removed the disk from the startup procedure from another node of the cluster.</description>
      <pubDate>Wed, 15 Mar 2006 03:52:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967257#M75005</guid>
      <dc:creator>vladky</dc:creator>
      <dc:date>2006-03-15T03:52:19Z</dc:date>
    </item>
    <item>
      <title>Re: Mount timeout</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967258#M75006</link>
      <description>We check the existance of disks prior to mounting them with the usual F$GETDVI calls (EXISTS,AVL) and perform the real mount in parallel subprocesses.&lt;BR /&gt;The master waits a specific time for the subs to complete and then continues.&lt;BR /&gt;&lt;BR /&gt;egards Kalle</description>
      <pubDate>Wed, 15 Mar 2006 03:55:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967258#M75006</guid>
      <dc:creator>Karl Rohwedder</dc:creator>
      <dc:date>2006-03-15T03:55:25Z</dc:date>
    </item>
    <item>
      <title>Re: Mount timeout</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967259#M75007</link>
      <description>Vladky,&lt;BR /&gt;&lt;BR /&gt;you're using MOUNT/NOASSIST during startup, aren't you ? If not, you should.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Wed, 15 Mar 2006 03:59:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967259#M75007</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2006-03-15T03:59:26Z</dc:date>
    </item>
    <item>
      <title>Re: Mount timeout</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967260#M75008</link>
      <description>Booting a production system with 1 disk missing can be dangerous if the application can not handle it.&lt;BR /&gt;&lt;BR /&gt;We use a special system parameter to allow a reboot with disks missing (USERD2). So, special action is needed.&lt;BR /&gt;&lt;BR /&gt;BTW : may be there is some dcl around the mount that is redoing the mount. We have. &lt;BR /&gt;&lt;BR /&gt;Wim&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Mar 2006 04:16:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967260#M75008</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2006-03-15T04:16:25Z</dc:date>
    </item>
    <item>
      <title>Re: Mount timeout</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967261#M75009</link>
      <description>Thanx for all your suggestions. I think the best way is to use /NOASSSIST with the mount command.&lt;BR /&gt;&lt;BR /&gt;Vladky</description>
      <pubDate>Wed, 15 Mar 2006 04:43:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967261#M75009</guid>
      <dc:creator>vladky</dc:creator>
      <dc:date>2006-03-15T04:43:01Z</dc:date>
    </item>
    <item>
      <title>Re: Mount timeout</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967262#M75010</link>
      <description>Vladky,&lt;BR /&gt;&lt;BR /&gt;definitely YES. MOUNT/NOASSIST should never hang, it will return with an appropriate error, if the disk cannot be mounted. Make sure there is a SET NOON in your SYSTARTUP_VMS.COM&lt;BR /&gt;&lt;BR /&gt;If you have a hanging MOUNT/ASSIST during startup (in another node in a cluster), you may be able to use an REPLY/TO=n ABORT operator command on one of the other nodes to abort the MOUNT OPCOM request.&lt;BR /&gt;&lt;BR /&gt;With recent versions of OpenVMS, you could also do a STOP/IMAGE/ID=&lt;PID&gt; to $FORCEX the mount image and still have your SYSTARTUP_VMS.COM continue&lt;BR /&gt;&lt;BR /&gt;If you would be running AMDS (started early in SYLOGICALS.COM or SYSTARTUP_VMS.COM), this could also help in a situation like that, as it allows you to force an image exit.&lt;BR /&gt;&lt;BR /&gt;Volker.&lt;/PID&gt;</description>
      <pubDate>Wed, 15 Mar 2006 04:51:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967262#M75010</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2006-03-15T04:51:03Z</dc:date>
    </item>
    <item>
      <title>Re: Mount timeout</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967263#M75011</link>
      <description>use noassist with the mount command.</description>
      <pubDate>Wed, 15 Mar 2006 04:51:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mount-timeout/m-p/4967263#M75011</guid>
      <dc:creator>vladky</dc:creator>
      <dc:date>2006-03-15T04:51:25Z</dc:date>
    </item>
  </channel>
</rss>

