From:	MERC::"uunet!CRVAX.SRI.COM!RELAY-INFO-VAX"  7-JUL-1992 02:51:02.41
To:	info-vax@kl.sri.com
CC:	
Subj:	RE: MncVerifyTimeout status - any cure?


In article <920627163159.21a078d1@cmt.anl.gov>, OSUDAR@cmt.anl.gov (John Osudar {708 252-7505}) writes:
|>The program that's attached below has worked for me when I've had disks go into
|>MntVerifyTimeout.  (We try to avoid having that situation, by setting the 
|>MVTIMEOUT parameter to its maximum of 64000 seconds -- but there have been
|>times when nobody's noticed that a disk has gone away for more than 17 hours!)
|>This program requires that you look up the disk's UCB address using
|>ANALYZE/SYSTEM -- mainly because I was too lazy to write the code required to
|>track down the UCB given the device name.
|>

I've taken the liberty of making John's program accept the device name so
that you needn't use SDA to find the UCB address.  No warranty expressed
or implied and all that jazz.


|>
|>	.title		unmvt -- undo mount-verify timeout
|>	.library	/sys$share:lib.mlb/
|>	$ucbdef
|>	$vcbdef
|>;
|>cmdlin:	.ascid		/????????/
|>prompt:	.ascid		/Disk name: /
|>done:	.ascid		/Done/
|>error:	.ascid		/Error/
|>;
|>	.entry	unmvt,0
|>	pushaw	cmdlin
|>	pushaq	prompt
|>	pushaq	cmdlin
|>	calls	#3,g^lib$get_foreign
|>	blbc	r0,8$
|>	clrl	-(sp)
|>	pushab	doit
|>	calls	#2,g^sys$cmkrnl
|>	pushaq	done
|>	blbs	r0,9$
|>8$:	movaq	error,(sp)
|>9$:	calls	#1,g^lib$put_output
|>	movl	#1,r0
|>	ret
|>;
|>	.entry	doit,^m<r2,r3>
	jsb	g^sch$iolockw
	movaq	cmdlin,r1
	jsb	g^ioc$searchdev
	blbc	r0,10$
|>	bisl	#ucb$m_valid,ucb$l_sts(r1)
|>	movl	ucb$l_vcb(r1),r2
|>	bisb	#1@vcb$v_mountver,vcb$b_status2(r2)
10$:	jsb	g^sch$iounlock
	setipl	#0
|>	movl	#1,r0
|>	ret
|>	.end	unmvt
|>
--
-----------------------------------------------------------------------------
Richard Critz					      critz@star.enet.dec.com
      -- I speak only for myself; I make no commitments for Digital. --
-----------------------------------------------------------------------------

