Enter your search terms Submit search form
	Web pdp-10.trailing-edge.com

                     DSKRAT BEWARE FILE



I.  Requirements for Lost Block Recovery Routine

    In order for the Lost Block Recovery code to  be  called
    the following conditions must be met.

        1)  Bit  35  of  word  17  of  table   11   (Monitor
            Configuration  Table)  must  be  set.   In other
            words, a "SET SCHED 1,3, or 7 must be in effect.

        2)  You must be the only job running.

            The following two messages will be output on the
            TTY in event of a failure.

            % LOST BLOCK RECOVERY WILL NOT BE DONE
            % LOST BLOCK RECOVERY PHASE ABORTED

            followed  by  one  or  more  of  the   following
            messages

            1)  GETTAB UUO FAILURE
            2)  MORE THAN ONE JOB LOGGED IN
            3)  SET SCHEDULING FOR NO MORE LOGINS
            4)  YOU ARE NOT A PRIVILEGED JOB
            5)  ANOTHER JOB IS RUNNING
            6)  CURRENT SCHEDULING MAY ALLOW ANOTHER JOB TO LOG IN

          The last two lines  are  output  when  the  Lost  Block
          Recovery  routine  is finally called and a second check
          is made on the system status.

          The following messages will  be  output  upon  internal
          error conditions in the LBR routine.

            1)  ?  OPEN FAILURE FOR DEVICE STR
                DSKRAT couldn't OPEN the device for output
            2)  ?  ENTER FAILURE FOR DEVICE STR
                DSKRAT couldn't ENTER one of its LSTBLK files
            3)  ?  INPUT FAILURE FOR DEVICE STR
                DSKRAT couldn't read the RIB of the  LSTBLK  file
                it has just created.
            4)  ?  ERROR IN OUTPUTTING TO LOST BLOCK FILE
                DSKRAT encountered an error while doing  a  SUPER
                USETO to one of its LSTBLK files.
            5)  ?  ERROR IN CLOSING LSTBLK FILE
                DSKRAT couldn't CLOSE a LSTBLK file.

	DSKRAT BEWARE FILE                                                                           Page 2


II  PRECAUTIONS AND RECOVERY PROCEDURES

    Upon successful completion of DSKRAT and the LBR Routine  the
    user  should  run DSKRAT again, preferably by-passing the LBR
    code.  This may be accomplished by either running  the  FIELD
    IMAGE version of DSKRAT which currently does not have the LBR
    routine or by failing to meet the LBR  requirements  for  LBR
    entry,ie.   Set  scheduling to 0 or log in another job.  Both
    listings should then be compared to determine if recovery was
    truly successful.

    Successful recovery  would  be  indicated  by  the  following
    conditions.

            1)  There are no Lost Blocks remaining.
            2)  There are no more Multiply defined clusters  than
                there were before.
            3)  There are no more Free clusters than  there  were
                before.

            If the above is true the operator may  simply  delete
            LSTBLK.*.

            In the event that the above is not true an SPR should
            be  submitted  stating the particulars of the failure
            along with the following:

            1)  Any available TTY output.
            2)  Both DSKRAT listings.
            3)  A DECtape with any generated LSTBLK files.



                              *****************WARNING****************

            If severe errors are indicated the  deletion  of  the
            LSTBLK  files  may result in a CRASH and/or necessity
            for refreshing the structure involved.


            To "gracefully" recover or to undo what has been done
            the  operator  must  delete  the  LSTBLK  files via a
            SUPER-USETO.  It is suggested that the program DELFIL
            be used with the following command line:
            *STR:LSTBLK.EXT/S