HP 3000 Manuals HP 3000 Manuals
Recovery From "OUT OF DISK SPACE" During UPDATE
Fred Parkes
Computer Systems Division
This MPE/iX release includes changes to UPDATE that allows UPDATE to skip
any file if it cannot (for any reason) be added to LDEV1. This means
that it is now possible to recover from "OUT OF DISK SPACE" during
UPDATE. You will see error and status messages on the console at the
point the file is skipped. There is also an error message at the end of
UPDATE that provides some information and direction.
What You See
At the end of UPDATE, when the system normally boots, the system will
stop. The operator must boot the machine manually. Messages will stay
on the console. The console will have a form of the following message on
it.
___________________________________________________________________________________
| |
| |
| ERROR. |
| |
| This UPDATE did not restore all files from the tape. (UPDERR 1001) |
| There were # files not restored because of out of disk space. |
| There were # files not restored for other than disk space reasons. |
| |
| There is more information about the error conditions in previous messages. |
| START the system, create more free disk space and run this UPDATE again. |
| Correct the problems and run this UPDATE again. |
| Correct the problems, START the system, create more free disk space and |
| run this UPDATE again. |
| END of LOAD(update). |
| |
| |
___________________________________________________________________________________
What You Should Do
If files have been skipped during an update, follow these steps to
correct the problem:
1. Determine the reason the files were skipped.
2. Start the system.
3. Correct the problem.
4. Shut the system down.
5. Do the update again.
6. After all files on the SLT have been restored to disk, continue
with the task at hand.
Files Skipped Because Out of Disk Space.
If there were one or more files skipped because out of disk space, look
at the messages on the console to determine which files were skipped. If
the files ISL.MPEXL.SYS, MMSAVE.MPEXL.SYS, and START.MPEXL.SYS have been
restored to disk:
1. Boot the system.
2. Free some disk space on LDEV1.
3. Shut the system down.
4. Redo the update from the same tape.
The files ISL.MPEXL.SYS and MMSAVE.MPEXL.SYS are small so there should
not be a problem restoring them.
The file START.MPEXL.SYS is large but has been given special
consideration. Instead of just skipping it, the file DUMPAREA.MPEXL.SYS
is purged (by UPDATE) to make room for START.MPEXL.SYS. Under any
reasonable conditions the file START.MPEXL.SYS is written to disk and
there is at most only one file skipped.
Reasonable conditions are: the file DUMPAREA.MPEXL.SYS can be purged to
make room for START.MPEXL.SYS and there are no other problems. If the
file DUMPAREA.MPEXL.SYS is purged, it will be replaced by UPDATE when
enough disk space is available.
Files Skipped Because of Other Reasons.
If there were files skipped for other than disk space reasons, determine
the cause. There will be error messages and status on the console. When
a call to HPFOPEN returns an error status, that status is always
displayed on the console. This is the key to the cause of the problem.
These error statuses are the same statuses that any caller to HPFOPEN can
receive. Whatever the problem, it must be corrected.
1. Correct the problems that have been found.
2. If there are still problems to correct, start the system and
correct them.
3. If you started the system, shut the system down.
4. Update again from the same tape.
Missing Messages.
If error messages have scrolled off the screen and you need the
information, try the update again. The same conditions should exist and
the same messages should be generated.
Mix and Match.
If a system experiences a problem and files have been skipped, the system
on disk is complete except for the skipped file or files. It is safe to
start the operating system. The system will not be a mixed system on
disk. The process of replacing files consists of first purging the old
file and then creating the new file. Any errors that occur are found
between the point where the old file is purged and the new file is
created.
If This Does Not Work
If the steps above do not resolve the problem, contact your support
representative. Trained Hewlett-Packard response center engineers can
recover some systems.
Things to Remember
When to Continue.
If you have experienced problems during UPDATE, you can continue when the
following conditions are met:
* UPDATE has completed successfully.
* All files from the SLT have been restored to disk.
* The system is up and running.
* There is some free space on LDEV1.
Reserving Contiguous Disk Space for UPDATE.
Before starting UPDATE you are asked to reserve an amount of contiguous
disk space in the file AXLDEV1.PUB.SYS. This amount is at least 60,000
sectors but may be larger. The prudent way to reserve this space is in
one contiguous block. Reserving this space in more than one block has
the affect of causing fragmentation. It introduces a risk that Secondary
Storage Manager (SSM) will allocate space for files on LDEV1 in a way
that causes an "out of contiguous disk space" condition during UPDATE.
Always try to reserve this contiguous disk space for UPDATE in one block.