Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!ncar!ames!sgi!shinobu!odin!anchor!olson
From: olson@anchor.esd.sgi.com (Dave Olson)
Newsgroups: comp.sys.sgi
Subject: Re: dvhtool error during upgrade
Message-ID: <1991Jan4.190724.17289@odin.corp.sgi.com>
Date: 4 Jan 91 19:07:24 GMT
References: <1991Jan3.220758.17838@eagle.lerc.nasa.gov>
Sender: news@odin.corp.sgi.com (Net News)
Distribution: usa
Organization: Silicon Graphics, Inc.  Mountain View, CA
Lines: 61

In <1991Jan3.220758.17838@eagle.lerc.nasa.gov> xxwrp@picasso.lerc.nasa.gov (Bill Palenske) writes:

First, this is documented pretty clearly in the release notes.  I know
the release notes are long, with lots of stuff most people don't care
about, but I really would recommend reading them before installing...

| 	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. )
Yes.
| 
| 	/etc/dvhtool -v creat /root/stand/sash sash $rbase $vhdev
| 
| 	Later on I got the same sort of message for symmon.  
| 
| 	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? 

The binaries that were there are still there, so you have an older
version of sash and symmon, which is rarely a problem.  One of the
'solutions' mentioned in the release notes is to just leave things
alone.  There were no significant bug fixes in either program.

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

It happened because (almost certainly) your disk was originally setup
by the factory or you under IRIX 3.1.  At that time, symmon wasn't
being shipped, and the default volume header size wasn't made large
enough to allow for it in all cases.  It may be that you already had
symmon installed, but that sash, ide, and symmon grew just enough larger
to cross the boundary of the available space.  I would remove symmon
if present, and not re-install it, since it appears that you don't need
it (see below).

| 	BTW, what does symmon do?

symmon is the kernel symbolic debugger.  It appears that at sometime
you chose to install the subsystem containing the kernel debugger,
either through step mode, or by choosing 'all'.  It appears that you
aren't using the kernel debugger, so I would simply remove the subsystem,
thus giving you more disk space.  You'll need to remove symmon from
the volume header yourself with dvhtool.

NOTE: All PI's shipped with 3.2 were inadvertantly shipped with symmon
in the volume header (but not in /stand) through an error in the
system burnin process.  So if you have symmon in the volume header,
but not on the disk, you might as well remove it to prevent confusion
and possible out of space messages with the command:
	dvhtool -v d symmon -v l

--

	Dave Olson

Life would be so much easier if we could just look at the source code.