[1387] in Release_7.7_team
Re: IRIX 6.2 update can fail if disk volume header is too small
daemon@ATHENA.MIT.EDU (Robert A Basch)
Mon Jul 27 13:05:14 1998
To: Robert A Basch <rbasch@MIT.EDU>
Cc: release-team@MIT.EDU
In-Reply-To: Your message of "Fri, 24 Jul 1998 12:53:14 EDT."
<199807241653.MAA08238@kiko.mit.edu>
Date: Mon, 27 Jul 1998 13:05:09 EDT
From: Robert A Basch <rbasch@MIT.EDU>
> IRIX 6.2 requires an up-to-date sash (boot loader) in the disk volume
> header; we thus always update it prior to booting the 6.2 miniroot.
> On paddington, an R4400 Indy, the volume header wasn't big enough to
> hold the new (larger) sash, thus breaking the miniroot boot. (The
> miniroot booted in a crippled state; most important, AFS didn't start).
> Since increasing the size of the volume header means a repartition of
> the disk, the best recourse at that point is to reinstall.
We could detect this failure earlier by doing the volume header update
in update_ws, and bombing out if it fails. The other R4400 I looked at
seems likely to have the same problem (it won't be taking the update
anyway); I have no idea if any other Indy is susceptible. (No other
machine that's been updated has had this problem).
Any thoughts as to whether we should add the volume header update/check
to update_ws?
Bob
