For 10.20, HP-UX now supports local root file systems of types HFS and JFS
(Veritas VxFS). In prior releases, a local root file system had to be
type HFS.
File systems in which the local root file system is a whole-disk file system
are not affected. These file systems remain type HFS. File systems
used for NFSD Diskless clusters, in which the root file system is an NFS
mount to a file system tree on a server, are not affected.
/stand Directory |
 |
The major change to HP-UX system architecture is that the directory
/stand will be created as a separately mounted file system.
/stand will always reside on the first logical volume on the bootdisk.
The /stand directory,
first implemented in a previous 10.0 release, contains the system kernel
and I/O mapping files that are required at boot time. In addition,
the directory also contains
kernel configuration and generation files.
If the
directory /stand is a separate file system, it must be of type HFS.
The root file system (directory "/") can be of type HFS or JFS.
Also, if /stand is a separate file system, an entry corresponding
to this file system must be maintained in the file /etc/fstab.
This entry is created when HP-UX is installed and must be maintained.
Removing this entry might result in a non-functional system.
The directory /stand is now explicitly mounted in user space at
startup time, with the mount operation performed in the startup script
/sbin/ioinitrc. Because ioinitrc is the first operation
performed from entries in
/etc/inittab, this is done at the beginning of user space
initialization.
/stand/rootconf will be used for recovering the system, so
you should not delete or modify this file.
Rebooting |
|
To reboot a system after replacing the kernel, the kernel should be
placed in the /stand directory only. If the kernel is placed
under /, the secondary loader hpux(1M) will not be able
to read the new kernel because /stand
and / are different file systems.
Mirroring |
|
If the boot volume and the root volume need to be mirrored,
the boot volume should be mirrored first. That is, the
lvextend(1M) command should be used for the boot volume
before it is used for the root volume. Both the boot and the
root volume need to be mirrored because mirroring only one volume
will not allow the system to boot from the mirror.
Boot Messages |
|
During the maintenance mode boot, the console will display
three messages stating that /stand could not be mounted
and the logical volume used for /stand could not be found.
These messages can be ignored.
System Recovery |
|
During an HP-UX system recovery, the following files may be needed
to be restored from the backup.
/stand/rootconf
/etc/lvmtab
/etc/fstab
/stand/ioconfig
|
These files should be backed up using any of the following
utilities: tar, cpio, or fbackup.
If you do not have a backup copy of these files, your system may be
unrecoverable.
Local Root File Systems |
|
For local root file systems, changes were made to hpux(1M)
(which is the Secondary System Loader (SSL)) and kernel and user-space
startup software to support the features described above.
At boot time, hpux(1) looks for a bootable kernel on HFS
volumes in one of these directories:
/stand/<kernel_name> -- for
the case of an HFS root and no separately mounted /stand file system
/<kernel_name> -- for
the case of a separately
mounted /stand file system (for HFS root, as well as JFS root)
User-Space Startup Software |
|
User-space startup software has been changed to remove implicit
assumptions that the root file system is of type HFS and also to
explicitly mount the /stand directory. All startup checks for
file system consistency (fsck and fsclean checks) have been retained.
However, these tests have been modified to first determine the type of
file system and then to invoke the correct utility appropriate for
that type of file system. Startup programs and scripts are now
independent of the file system type of the root file system.
Kernel Support |
|
Kernel support of JFS file systems was present in earlier releases;
the kernel now also supports JFS file systems as the root file system.
Compatibility |
|
User software should be completely independent of this functionality.
All HP-UX system administration tools have been internally modified
to support this functionality. You can continue to operate
with whole-disk or HFS-only file systems as before.
Printable version
