|
|
HP 3000 MPE/iX Release 6.0 System Software Maintenance Manual (Release C.60.00): HP 3000 MPE/iX Computer Systems > Chapter 3 Planning for Your Task3.6 Estimating Disk Space |
|
Read the subsections in this section:
Before you begin to modify your system software make sure that you have enough disk space to update your system. Modifying system software includes: updating the version, reinstalling your system software, adding on purchased products from the SUBSYS tape, or applying patches. There are three types of disk space requirements that are referenced during the modification process:
Table 3-5 “Non-Contiguous Disk Space Sectors” "Non-Contiguous Disk Space Sectors," lists the amount of non-contiguous disk space sectors required for the three operating system components (SLT, FOS, SUBSYS) and PowerPatch of the currently supported versions of the operating system software. During the modification process, some files are duplicated temporarily, and sometimes older versions of files are retained temporarily. This causes the "in process" (or peak) amount of disk space usage to be greater than the "final" (or net) amount of disk space usage when the modification is complete. You must have the peak amount of disk space available on your system during the process to successfully modify your system. The combined System Load Tape (SLT) and Fundamental Operating System (FOS) are the minimum requirements for any system software version. Ensure that you have enough room on LDEV 1 for all the SLT files. The FOS files do not have to go onto LDEV 1. Table 3-5 Non-Contiguous Disk Space Sectors
There are several conditions under which you need additional non-contiguous disk space. Refer to the appropriate following subsection for information on estimating non-contiguous disk space for your specific task.
To estimate the amount of additional permanent (net) non-contiguous disk space required to update your system software, subtract the value for your current version from the value for the version you are updating to. Record the disk space sectors required for the Update on your checklist. The values are listed in Table 3-5 “Non-Contiguous Disk Space Sectors” "Non-Contiguous Disk Space Requirements," for the SUBSYS (purchasable subsystem products) are the maximum for all possible purchasable products. Estimate purchased product (SUBSYS) disk space based on the number and kind of software subsystem products that you purchased. If you are not adding-on any new purchased products, the disk space sectors currently being used by your existing products will remain the same. Record the estimated disk space required for SUBSYS products on your checklist. The disk space required is listed in the section, "Disk Space Requirements," in the Read Before Installing that comes with the PowerPatch or Express media. Record the disk space required for the PowerPatch or Express on your checklist. Reactive patches vary extensively in the amount of disk space they require. Reactive patches usually replace existing files, and the increase in disk space is very little. If you want to make a worst case estimate for disk space, use the amount of disk space used by the reactive patch and add that to the disk space requirement for LDEV 1. Record the estimated disk space required for Reactive patches on your checklist. When you have created a staging area on your local system, you can distribute that staging area to a remote system, provided the two systems match. Both systems must match OS versions, relevant SUBSYS products, and applied patches. To estimate the amount of disk space required on the remote system for a staging area that resides on your local system:
If your products are listed in MBytes, particularly third-party products, calculate the disk space sectors by performing this conversion: n Mbytes × 1,000,000 sectors/256 bytes = m sectors where: n-the number of Mbytes m-the number of sectors
Therefore the disk is a 2,000 Mbyte disk, (also known as 2 GByte disk). For a closer estimate, use the value 1,048,576 instead of 1,000,000. For a quick estimate, use the value 4,000 instead of 1,000,000/256. The maximum amount of contiguous disk space sectors required to complete a system modification on any system is approximately:
Use CHECKSLT to estimate the amount of contiguous disk space sectors required to complete a system modification on your system. Use DISCFREE to see how much free space you have on your system. If you are performing an Update with Tape or Modify Remote System task, and you want to have a closer determination of contiguous disk space for AXLDEV1, proceed to Step 1 to determine the disk space required by the UPDATE tool. Otherwise, proceed to the subsection, "Disk Space Error Messages." Update with Tape, Modify Remote SystemTo determine the amount of contiguous disk space sectors required by the UPDATE tool:
The update tools (UPDATE,AUTOINST, HPINSTAL, and Patch/iX) that modify your system require a minimum amount of contiguous sectors of disk space on LDEV 1 and non-contiguous sectors on the system volume set to ensure a successful modification process. These disk space sectors are a subset of, and are included in, the peak usage disk space requirements. The default disk space requirements are listed in Table 3-6 “Update Tool Disk Space Default Requirements”. Table 3-6 Update Tool Disk Space Default Requirements
The tools search for the default disk space during the modification process. At any point in the process, if the tool does not find the disk space it requires, you may see an error message. The error messages and responses required vary depending upon when they occur in the modification process. For additional information, refer to Appendix C “Managing Disk Space” and Appendix H “Error Messages and Warnings”
|
|