[Info-vax] Uptime for OpenVMS

[Bob Koehler]

In article <paul.nospam-AC81E2.11340318052011 at pbook.sture.ch>, Paul Sture <paul.nospam at sture.ch> writes:
> 
> I believe it was Larry Kilgallen who related the tale of how mount 
> verification came into being.  IIRC the tale went that a new and junior 
> member of VMS Engineering took a disk out without dismounting it first, 
> causing some disruption.  Instad of being screamed at, the offender got 
> told to address the problem, and mount verification was the outcome.

   Yes, I recall that story. (But not who from).

   On the other hand, I've seen an 11/780 run for many minutes after
   it's system disk was pulled by accident (somebody swapped the
   unit plugs on the first two RP06).  Then errorlog tried to put a time
   stamp in the error log file, the failure was reported to OPCOM which
   reported it on the console and tried to log it in the operator log.
   Both write attempts caused errorlog to try to record disk I/O
   failure, ...

   The only thing that allowed other processes to keep going was the slow
   speed of the LA36 console, which held up OPCOM from chewing up too
   much CPU time as it worked on it's growing backlog of messages.