Installation is the second of four steps necessary to the successful implementation of DMF at a site:
Planning
Installation
Configuration
Initialization
The planning, configuration, and initialization steps, as well as daily operation, are described in the DMF Administrator's Guide for IRIX.
The procedures described in this document are used for the installation of major releases, revisions, and product upgrades delivered on the release media.
All installation steps are initiated through the SGI inst utility and the dmmaint utility.
Beginning with DMF release 2.7, the installable DMF package includes a server software subsystem and a client software subsystem. The server software subsystem provides the full set of DMF functionality, including the DMF daemon, MSPs, LSs, DMF user and administrator commands, DMF online manuals, and all DMF man pages. The client software subsystem provides the executable files, libraries, and the subset of man pages that allow a machine to be a DMF client. This subsystem allows users on the client to use the DMF distributed commands. Only one of these subsystems can be installed on a machine.
Before beginning the installation of DMF, ensure that you meet the following requirements:
You must be root
The Data Management API (DMAPI) is the mechanism within IRIX and the XFS/CXFS file system for passing file management requests between the kernel and DMF. Ensure that you have installed DMAPI and the appropriate patches on the DMF server, as listed in the files displayed by the Dependencies and News buttons on the dmmaint (8) display.
Caution: For file systems to be managed by DMF, they must be mounted on the DMF server to enable the DMAPI interface. You can do this by using the mount -o dmi command or by declaring parameter 4 in the fstab entry to be dmi. (refer to the man pages for mount or fstab). Failure to enable dmi for DMF-managed file systems will result in a configuration error.
DMF state information is kept within a file system structure called an extended attribute . Extended attributes can be either inside the inode or in attribute blocks associated with the inode. DMF runs much faster when the extended attribute is inside the inode, because this minimizes the number of disk references that are required to determine DMF information. In certain circumstances, there can be a large performance difference between inode-resident extended attribute and non-resident extended attribute.
You should configure your file systems to ensure that the extended attribute is always inode-resident. This is done with the mkfs_xfs command. Declare the inode size to be 512 bytes using the -i size=512 option. File systems that already exist will have to be dumped, recreated, and restored. This change is not mandatory.
Ensure that, in the operating system configuration file, the following IPC kernel configuration parameters are set equal to or greater than the default: MSGMAX, MSGMNI, MSGSEG, and MSGSSZ. The parameters are described in Appendix A of IRIX Admin: System Configuration and Operation, SGI publication 007-2859.
When you have completed the installation, you must configure DMF on the server prior to using it. See the DMF Administrator's Guide for IRIX for information on configuring DMF.
The following diagram shows the DMF directory structure on server machines. The dmmaint command creates links in other directories that are not shown in this diagram. It also copies files into other directories that are not shown in this diagram.
There is more than one version directory if you upgrade DMF from a previous release. When you use the dmmaint(8) utility, you can activate the most recent version and configure it. You can also use dmmaint to activate any version you wish.
The News and Readme files are displayed by the News and Dependencies buttons on the dmmaint(8) display.