home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vms
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!rpi!batcomputer!vger.cheme.cornell.edu!OLIN
- From: olin@vger.cheme.cornell.edu (Steve Thompson)
- Subject: Re: Mount verification timed out
- Message-ID: <1992Dec29.222049.21075@tc.cornell.edu>
- Sender: news@tc.cornell.edu
- Nntp-Posting-Host: vger.cheme.cornell.edu
- Reply-To: olin@vger.cheme.cornell.edu
- Organization: Chemical Engineering, Cornell University, NY
- References: <1992Dec29.152302.1716@das.harvard.edu> <1992Dec29.115919.4181@arizona.edu>,<1992Dec29.215329.8795@das.harvard.edu>
- Distribution: world,local
- Date: Tue, 29 Dec 1992 22:20:49 GMT
- Lines: 26
-
- In article <1992Dec29.215329.8795@das.harvard.edu>, chen@speed.uucp (Lilei Chen) writes:
- >In article <1992Dec29.115919.4181@arizona.edu> Leonard@Arizona.EDU writes:
- >>Boost the value of the SYSGEN param MVTIMEOUT. (By default 3600 sec. =
- >>1 hour.) We have ours set to the maximum, which is 64000 sec (a little
- >>under 18 hours), which should give your rebooting node enough time to
- >>come back up and start re-serving the disks.
- >>
- >>Aaron
- >
- >The problem occures even when the node is down for 5 minutes. I am not
- >sure what MVTIMEOUT really does.
- >
- >Jim
-
- Is it possible that the node being shut down does a DISMOUNT/CLUSTER?
- You'd only want the /CLUSTER qualifier if the node wasn't coming back
- up shortly.
-
- Steve
-
- ---------------------------------------------------------------------------
- Steve Thompson, System Mangler Internet: thompson@cheme.cornell.edu
- School of Chemical Engineering Bitnet: thompson@crnlchme
- Olin Hall, Cornell University Phone: (607) 255 5573
- Ithaca NY 14853
- ---------------------------------------------------------------------------
-