Planning to Configure into your System a Disk Already Containing Data

When configuring a new disk onto either Series 700 or 800 system, both SAM and insf now treat the disk in its entirety and create a single block device special file in /dev/dsk and a single character device special file in /dev/rdsk. As of HP-UX 10.0, to apportion disk space on both Series 700 and 800 systems, use Logical Volume Manager (LVM), which is documented in the Managing Systems and Workgroups manual.

Configuring a disk already containing data into HP-UX 10.0 requires some attention to detail, because the I/O system is largely converged and the HP-UX file system layout (that is, the locations of system files and directories) has changed.

Approach the task in two stages:

Examine the files and data on the disk for possible clashes with the HP-UX 10.0, and take the necessary precautions, as documented in “Ensuring Against Clashes with HP-UX 10.0”, the next section.
Configure the disk into HP 10.0.

Once 9.x Series 700 whole disks and Series 800 disks with hard partitions are successfully configured, HP-UX 10.0 accesses their data using a compatibility pseudo-driver (cpd).

Ensuring Against Clashes with HP-UX 10.0

Before you configure a disk containing 9.x data to a 10.0 system, it is essential that you make sure you will not be introducing file-system inconsistencies. This precaution is necessary because the file-system layout has changed dramatically from HP-UX 9.x to 10.0. Former system files and device files will not work in the new operating system and might cause serious problems if they are used.

The new file-system hierarchy is based on AT&T V.4 and OSF/1. The organization of files and directories are explained in a white paper entitled HP-UX 10.0 File System Layout.

To ensure against incompatibilities with HP-UX 10.0:

Examine the files on the 9.x disk to make absolutely sure you do not mount system directories and structural files. System directories include /usr, /dev, /etc, /system, /bin, and /lib. Structural files include files such as /etc/checklist and dfile. Never attempt to use 9.x device special files on a 10.x system. They will fail. Delete or rename any system files and directories you find.
Examine user scripts for occurrences of 9.x-specific path names and commands that are invalid or obsolete for 10.0. Do this before mounting the 9.x disk.
HP has some tools on 10.0 to help identify and correct changed or unsupported path names. These tools are shipped in the following filesets:
- Upgrade.UPG-ANALYSIS
- Upgrade.UPG-MAN
On a 10.0 system, the tools are installed in the /opt/upgrade/bin directory. The manpages are installed in /opt/upgrade/share/man. If you have obtained the filesets to be loaded onto an 9.x system, the filesets will be installed into /upgrade/bin and /usr/man.
Consult the manual, Moving HP-UX 9.x Code and Scripts to 10.x: Using the Analysis and Conversion Tools and the upgrade manpages for further guidance on preparing 9.x files for HP-UX 10.0.

Understanding How to Configure a Disk Already Containing Data

Accessing 9.x data might require that you configure one of the following 9.x disk types to HP-UX 10.0:

Series 700 disks using Software Disk Striping (SDS). SDS is not supported on HP-UX 10.0. The safest way to import 9.x data from an SDS disk is as follows:
1. Isolate the specific files of data.
2. Examine the files for presence of system and structural files (as documented in the previous section) and remove any invalid references.
3. Copy the information onto a 10.0-configured disk.
Series 700 whole disks.
1. Examine all files for the presence of system and structural files (as documented in the previous section) and remove any invalid references.
2. Configure the disk as documented in “Configuring into your System an Unpartitioned Disk Already Containing Data”, shortly. insf creates the required device special files to access the whole disks. If the disk is used in its entirety (as it was on 9.x), the data will be accessed using the cpd.
Series 800 disks with hard partitions/sections.
1. Examine all files for the presence of system and structural files (as documented in the previous section) and remove any invalid references.
2. Configure the disks with Series 800 hard partitions by following the procedure “Configuring into Your System a Partitioned Disk Already Containing Data”, later in this chapter. You will create device special files for each section using mksf or mknod. The cpd will enable you to access the partitioned data.
Series 800 LVM disks.
1. Examine all files for the presence of system and structural files (as documented in the previous section) and remove any invalid references.
2. Add Series 800 LVM disks to a 10.0 system by importing the LVM information, as documented in “Configuring into your System an LVM Disk Already Containing Data”.

Planning to Configure into your System a Disk Already Containing Data

Technical documentation

» Table of Contents

» Index

Ensuring Against Clashes with HP-UX 10.0

Understanding How to Configure a Disk Already Containing Data