Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!eagle!news
From: xxwrp@picasso.lerc.nasa.gov (Bill Palenske)
Newsgroups: comp.sys.sgi
Subject: dvhtool error during upgrade
Message-ID: <1991Jan3.220758.17838@eagle.lerc.nasa.gov>
Date: 3 Jan 91 22:07:58 GMT
Reply-To: xxwrp@picasso.lerc.nasa.gov (Bill Palenske)
Distribution: usa
Organization: NASA/Lewis Research Center, Cleveland
Lines: 30


	While upgrading a PI from 3.2 to 3.3.1, I got the following:

	Interrupt/Error:

	No room in volume header for sash.

	( I assume this really means what is says, and not: No room in 
	/tmp. )

	/etc/dvhtool -v creat /root/stand/sash sash $rbase $vhdev

	Later on I got the same sort of message for symmon.  

	(For what it's worth, binaries were copied to /stand.)

	This seems to imply, at least the possibility, that in standalone
	use sash and symmon would not be located in the volume header.  

	However, since I have not encountered any problems yet.  I guess 
	this means the old 3.2 sash and symmon are still in the vh
	and still work? 

	My questions are:  Why did this happen? and how do I fix it?

	BTW, what does symmon do?

	email will do, I will summarize.  Thanks.

	xxwrp@convx1.lerc.nasa.gov