DFS(TM) for AIX(R) and Solaris
PTF 11 README
Version 3.1
Document Number 00000-00
00000
First Edition (July 2006)
This edition applies to:
IBM DFS for Solaris 10, Version 3.1and to all subsequent releases and modifications until otherwise indicated in new editions.
This softcopy version is based on the printed edition of this book. Some formatting amendments have been made to make this information more suitable for softcopy.
Order publications through your IBM representative or through the IBM branch office serving your locality.
© Copyright International Business Machines Corporation
2001-2006. All rights reserved.
Note to U.S. Government Users -- Documentation related to restricted
rights -- Use,
duplication or disclosure is subject to restrictions set forth in GSA
ADP Schedule
contract with IBM Corp.
Obtaining
and Installing/Uninstalling the PTF
This README file describes the contents of the IBM DFS only for Solaris 10 Program Temporary Fix (PTF) 11 for version 3.1. This PTF is not packaged for AIX and Solaris versions other than Solaris 10. It also provides instructions for obtaining and installing the PTF on Solaris 10 platform.
This PTF must be applied to DFS Version 3.1.
The current software changes to DFS 3.1 are cumulative. That is,
this PTF includes the
changes that were issued in all previous PTFs. It is necessary to
install DFS 3.1 GA before installing this PTF.
You can download the PTF from the IBM Web site http://www6.software.ibm.com/dl/dfs31/dfs31-p. Follow the instructions on the Web site to download the PTF, and then follow these installation instructions to install the PTF on your system.
This section describes the procedure for installing the DFS 3.1 PTF 11 on a Solaris 10 machine. The PTF for Solaris has the file name dfs-3.1-solaris-P11.tar.Z.
Before installing the PTF, ensure that you have met all of the installation prerequisites described below:
uncompress [file_path]dfs-3.1-solaris-P11.tar.Z
tar xvf [file_path]dfs-3.1-solaris-P11.tar
Use of file_path is required if the PTF tar file is not in the current directory.
For information about various features of the installation script, see Installation script options.
To verify which packages were installed, issue the command pkginfo | grep IDFS
You can modify the behavior of the PTF installation script, installptf, by using command-line options or by setting up a customized environment file.
The complete format of the installptf script follows.
installptf [-e env_file] [-nolock] [-noback] [-force] [-help]
Options specified on the command line always override default options and definitions found in an environment file.
The PTF installation script reads several parameter values from its environment file, installptf.env. The environment file is located with the installation script in the IDFS-P10 directory. A customized environment file allows the administrator to change complex settings, such as file paths, that cannot be changed by using command-line options. For example, customizing the environment file to cause back-out PTFs to be uniquely named allows an administrator to store multiple uninstallation options; the installptf script's default behavior is to overwrite any existing back-out PTF with a new one.
To use a customized environment file with the PTF installation script, follow these steps.
By default, the installptf script creates a log file and a back-out PTF. Both of these artifacts are overwritten by subsequent PTF installations. The log file is stored in /var/sadm/patch/IDFS/. The back-out PTF contains archived versions of overwritten packages, a README file, and a script named backoutptf that reverses the actions taken by the installptf script for that machine. The backoutptf script is stored in /var/sadm/patch/IDFS/backout/ and must be executed from that directory.
This section highlights general information and requirements that apply to this PTF release for IBM DFS 3.1 for Solaris 10.
To find the latest information about this product, please refer to the following IBM Web site:
http://www-306.ibm.com/software/stormgmt/dfs
DFS 3.1 supports episode aggregate size only upto 1TB. If user tries to create episode aggregate on partition or logical volume with more than 1 TB size, then also DFS newaggr command creates aggregate of only upto 1TB size.
The following tips apply when upgrading DFS software to version 3.1 or installing a DFS 3.1 PTF.
After upgrading a DFS machine's operating system from Solaris 9 to Solaris 10, you must install DFS 3.1 PTF 11 on the Solaris 10 system regardless of whether the PTF was previously installed on the Solaris 9 system. The PTF 11 installation script detects the Solaris 10 operating system version and installs appropriate software packages for that system.
If the DFS autostart feature is enabled, you might see error messages after system is upgraded from solaris 9 to Solaris 10 because the DFS 3.1 GA software attempts to start on the Solaris 10 system before the PTF is installed. To avoid seeing these messages, disable the DFS autostart feature before upgrading the Solaris operating system. To disable autostart, issue the following command from a root prompt.
config.dfs -autostart no
After installing the DFS 3.1 PTF 11, enable autostart again by issuing the same command with the -autostart value set to yes.
cd /usr/bin
rm kinit klist kdestroy
ln -s /opt/dcelocal/bin/kinit kinit
ln -s /opt/dcelocal/bin/klist klist
ln -s /opt/dcelocal/bin/kdestroy kdestroy
If DCE is installed after the Solaris 10 operating system installation, these steps are unnecessary.
To do a new DFS installation on a Solaris 10 system using the DFS 3.1 GA software and the PTF 11, you must first install the DFS 3.1 GA software on the Solaris 10 system, then install the PTF 11 software. The PTF 11 supplies the necessary requirements for Solaris 10 support. Do not attempt to configure the DFS software until after the PTF software has been installed.
In some cases, after upgrading DCE and DFS software on Solaris machines, the DCE software does not start automatically when the machine is started. This is because a link to a DCE initialization file is missing after installation.
To solve this problem, create a link named S15-20dce in the path /etc/rc3.d/. The link should reference the file /etc/init.d/dce.
Before installing DFS Version 3.1 PTF 11 on Solaris 10 machine, ensure that a supported DCE 3.2 PTF 9 is installed on the system. DFS 3.1 for Solaris 10 requires DCE 3.2 PTF 9 onward. A supported DCE product(DCE 3.2 PTF 9) must be installed on the machine prior to installation of DFS 3.1 PTF 11 on Solaris 10. Please refer DCE release/announcement for supported DCE version on Solaris 10.
Installation procedures on Solaris platforms do not automatically enforce this requirement. The showrev -p command can be used to show patches that have been applied to your DCE software.
A command line interface similar to the UNIX man command is now available with DFS 3.1 on Solaris and AIX. The new dfsman commands enable users to read preformatted command reference files in the list3270 format. For example, issue the dfsman cm command to access the manual page on the DFS Cache Manager. For a list of all available dfsman commands, issue the dfsman help command.
Additionally, a new tool, asciiview.dfs, is now available to enable users to view the following documents:
If bak dump commands or bak dumpinfo commands are executed too closely in succession, errors may result.
These bak commands access the Backup Database for information on the dump schedule, the tape drive, and the DFS servers. To access the Backup Database, the bak process must obtain a lock. The lock is exclusive to the process and is not recursive. In other words, only one process can access the Backup Database at any given time. When a bak dump or bak dumpinfo command is issued, an instance ID is created. Simultaneous access to the Backup Database is prohibited, and the instance ID enforces this.
Each distinct dump command requests different information and uses different functions; therefore, the period of time for which the lock exists differs for each dump request. And, the period of time for which other processes are prohibited from accessing the database differs for each dump request. For this reason, the time interval between successful bak dump or bak dumpinfo commands varies.
DFS does not return an error the first time a locking conflict is encountered; instead, there is a sizable amount of time during which a locked out process retries to access the database. Therefore, if a lock is being held by another process when a bak dump or bak dumpinfo command is issued, DFS generally resolves the locking conflict. In the case that locking conflicts exist and cannot be resolved, DFS users receive an error specifying that a lock is held by another user. To resolve the problem when this error is received, stagger the execution times of the bak commands.
IBM DFS for AIX Quick Beginnings and IBM DFS for Solaris Quick Beginnings, included with DFS Version 3.1, give an incorrect file name in the file path for installed HTML documentation. The installed file has the extension .htm, but the file is incorrectly listed with the .html extension in the section titled "Viewing the HTML documentation."
The correct paths follow.
For AIX:
/usr/lpp/dfsdoc/html/en_US/index.htm
For Solaris:
/opt/dce/dfsdoc/html/en_US/index.htm
Instructions for creating the root.dfs fileset, which is the root of a DFS cell's filespace, were omitted from the DFS Version 3.1 Quick Beginnings guides. The instructions can be found in the DFS Administration Guide, in the "DFS configuration issues" section, under the heading "Setting up filesets."
The Quick Beginnings guides included with DFS Version 3.1 inappropriately recommend restarting the system as a way of shutting down DFS processes before a software upgrade. This method is not effective in most cases because DFS automatically restarts when the system restarts.
This error appears with the heading "Stopping Software Processes" in the "Installing DFS 3.1" section of the AIX and Solaris Quick Beginnings guides.
Before upgrading DFS software, stop all DCE applications, then stop any remaining DCE and DFS processes. After upgrading DFS software, restart the system before using DFS.
The need for the en_US locale on Solaris was not documented. Users should be aware that DFS 3.1 on Solaris 7, 8, 9 and 10 requires that the North American English locale (en_US) be installed on the host. This locale can be installed by the Solaris administrator at system installation. Alternatively, en_US locale support can be added to a pre-existing Solaris system. To find the Sun packages needed, go to the docs.sun.com Web site and search for "North America OS Support." Depending on the hardware architecture, the host might also need the package referred to as "North America 64 bit OS Support."
PTF 11 includes all updates that were in previous PTFs, plus bugs
fixed for porting issues on Solaris 10. It doesn't
include any new bug fixes other than Solaris 10 porting on top of DFS
3.1 PTF 10. Reference APAR for DFS 3.1 PTF 11 on Solaris 10 is
IY85394.
(c) IBM Corporation 2001-2006. All
Rights Reserved