PTF13 README

Fix readme


Abstract

PTF13 README

Content

PTF 13 README

DFS(TM) for AIX(R)
PTF 13 README

Version 3.1

Document Number 00000-00

00000

 

First Edition (November 2009)

This edition applies to:

IBM DFS for AIX 5.3 and AIX6.1 (6.1 and 6.1-TL02) Version 3.1 and 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-2005. 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.

Contents

Overview

Obtaining and Installing/Uninstalling the PTF

·       Uninstalling the PTF

 

Contents of the PTF

·  Product notes

·  Support for DCE 3.2

·  Support for AIX 6.1 and 6.1(TL-02)

·  Support for AIX 5.3

·  Support for TSM on AIX

·  Migration tips

·  DCE PTF is required when using DCE 3.1

·  Online manual pages now available

·  Specifying a time interval between successive bak dump or bak dumpinfo commands .

·  Quick Beginnings gives incorrect filename for HTML documentation

·  Creating the root.dfs fileset

·  System restart is inappropriate for stopping DFS

·  Use "Install Latest" option to upgrade DFS 3.1 on AIX

·  Working around the "missing prerequisite" installation error

 

 

 

·       Defects fixed in this PTF:-

 

·  Defects fixed in PTF 13

·  Defects fixed in PTF 12

·  Defects fixed in PTF 11

·  Defects fixed in PTF 10

·  Defects fixed in PTF 9

·  Defects fixed in PTF 8

·  Defects fixed in PTF 7

·  Defects fixed in PTF 6

·  Defects fixed in PTF 5

·  Defects fixed in PTF 4

·  Defects fixed in PTF 3

·  Defects fixed in PTF 2

·  Defects fixed in PTF 1

 



Overview

This README file describes the contents of the IBM DFS for AIX  Program Temporary Fix (PTF) 13 for version 3.1. It also provides instructions for obtaining and installing the PTF on each platform.

This PTF must be applied to DFS Version 3.1.  This PTF is available only for AIX5.3, AIX6.1 and AIX6.1-TL02 platforms.



Obtaining and installing the PTF

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 not necessary to install previous updates before installing this PTF. Some exceptions to this statement are:

DFS3.1 PTF 12 is the minimum level providing support on AIX6.1.

DFS3.1 PTF 12 is also the minimum level providing support on AIX6.1-TL02. Installation of DFS3.1 PTF13 is necessary before using DFS on AIX6.1-TL02 platform.

As AIX 5.3 support was added with the DFS 3.1 PTF 9 release, PTF 9 is the minimum level providing DFS 3.1 support on the AIX 5.3 kernel.



Obtaining the 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.



Installing the PTF

This section describes how to install the IBM DFS Version 3.1 PTF on AIX platform.

Installing the PTF on an AIX machine

This section describes the procedure for installing the DFS PTF on an AIX machine. The PTF for AIX has the following '.tar' files and free disk space requirement for different Operating Systems:

Operating System
  Installable '.tar' File
 Free Disk Space Required (Apprx)
          AIX 6.1(TL-02)
          dfs-3.1-aix61TL02-P13.tar
                  20 MB
          AIX 6.1
          dfs-3.1-aix61-P13.tar
     10 MB
          AIX 5.3
          dfs-3.1-aix53-P13.tar
      26 MB

Before installing the PTF, ensure that your system meets all of the installation prerequisites described below:

  • DCE (Distributed Computing Environment) Version 3.2 with PTF 1 or higher.
  • DFS Version 3.1.0.0 (GA release)
  • AIX operating system version 5.3 or 6.1
Using the PTF to enable AIX 6.1 and AIX 6.1(TL-02) support

The DFS 3.1 PTF 13 software includes new support for the AIX 6.1 and AIX 6.1 TL-02 operating system. The following upgrade paths were tested:

  • Installing DFS 3.1 PTF 13 on an AIX 6.1 system with the DFS 3.1 general availability (GA) software installed.
  • Upgrading an AIX 5.3 machine running DFS 3.1 and supported PTF 9 or higher to AIX 6.1 with DFS 3.1 PTF 12 followed by PTF 13. This installation should preserve the previous configuration.
  • Upgrading an AIX 5.3 machine running DFS 3.1 and supported PTF 9 or higher to AIX 6.1(TL-02) with DFS 3.1 PTF 12 followed by PTF 13. This installation should preserve the previous configuration.
  • Upgrading an AIX 6.1 machine running DFS 3.1 and supported PTF 12 to AIX 6.1(TL-02) with DFS 3.1 PTF 12 followed by PTF 13. This installation should preserve the previous configuration.

   There are three ways to upgrade machines from AIX 5.3 to AIX 6.1 or AIX 6.1(TL-02):
1. Overwrite - This overwrites the previous data and does a fresh installation of AIX 6.1. Previous data and configuration information is lost if this option is selected.
2. Preservation - This overwrites the data in /var, /usr, and / filesystem. Previous configuration information is lost.
3. Migration - This preserves all the data and configuration information.

We conducted the upgrade tests using the migration option.

The following tips are important for customers who install DFS software on AIX 6.1 and 6.1(TL-02) systems using the DFS 3.1 GA release and PTF 13.

Migration scenarios:-

Migration from a machine having OS version AIX 5.3 (with no PTF 13 installed) :-
1. After upgrading a DFS machine's operating system from AIX 5.3(with no PTF 13 installed) to AIX 6.1, you must install PTF 12 first and then PTF 13 on AIX 6.1. The PTF 13 installation is done using the smit on AIX 6.1 with the overwrite option selected. Do not start DFS or run DFS command until the PTF 13 software has been installed.
2. After upgrading a DFS machine's operating system from AIX 5.3(with no PTF 13 installed) to AIX 6.1(TL-02), you must install PTF 12 first and then PTF 13 on AIX 6.1(TL -02). The PTF 13 installation is done using the smit on AIX 6.1(TL-02) with the overwrite option selected. Do not start DFS or run DFS command until the PTF 13 software has been installed.

Migration from a machine having OS version AIX 5.3 (with PTF 13 installed) :-
3. While migrating the OS from AIX 5.3 to AIX 6.1, then:-

4. While migrating the OS from AIX 5.3 to AIX 6.1(TL-02) then :-      

·       Before migrating to AIX 6.1(TL-02), please remove PTF 12 and PTF 13 on AIX 5.3. Also, take a DFS backup as the mksysb utility is not supported by DFS 3.1 on AIX.  For more information, please refer to:- http://www-01.ibm.com/software/stormgmt/dfs/library/docs/31manuals/relnotes/durns008.htm#Header_54 )).

·       After migration, please install the DFS3.1 PTF12 and PTF 13(for AIX 6.1 TL -02) softwares using smit option. Do not start DFS or run DFS command until the PTF 13 software has been installed

Migration from a machine having OS version AIX 6.1 (with PTF 13 installed) :-
5. After upgrading a DFS machine's operating system from AIX 6.1 to AIX 6.1(TL-02) then :-

  • You must DE-INSTALL the former PTF-13 filesets using option “Reject Applied Software Updates (Use Previous Version)” first.
  • The PTF 13(AIX 6.1 TL-02) installation is done using the smit on AIX 6.1(TL-02) with the overwrite option selected. Do not start DFS or run DFS command until the PTF 13 software has been installed.
6. To do a new DFS installation on an AIX 6.1 system using the GA software and the PTF, you must first install the DFS 3.1 GA software on the AIX 6.1 system, and then install DFS3.1 PTF 12 software and then PTF 13. DFS 3.1 PTF 13 supplies the necessary requirements for AIX 6.1 support. Do not attempt to configure the DFS software until the PTF 13 software has been installed.
7. To do a new DFS installation on an AIX 6.1(TL-02) system using the GA software and the PTF, you must first install the DFS 3.1 GA software on the AIX -6.1 (TL-02) systems, and then install the PTF 12 software followed by PTF 13. DFS 3.1 PTF 13 supplies the necessary requirements for AIX 6.1(TL-02) support. Do not attempt to configure the DFS software until the PTF 13 software has been installed.
8. If the DFS autostart feature is enabled, you might see error messages during the upgrade process because the DFS 3.1 GA software attempts to start on the (AIX 6.1) system before PTF 13 is installed. To avoid seeing these messages, disable the DFS autostart feature before upgrading the AIX operating system. To disable autostart, issue the following command from a root prompt:
     config.dfs -autostart no

After installing DFS 3.1 PTF 13, enable autostart again if required by issuing the same command with the -autostart value set to yes.

Installing the DFS 3.1 PTF 13 on AIX 6.1
1. Become the local superuser root (Single-user mode is recommended).
2. Stop all DCE and DFS processes on the machine.
3. Ensure that you have PTF 12 installed on your machine with the COMMIT field set as NO (as this is useful for MIGRATION scenario in future).
4. Change to the directory where the PTF packages will be kept.
5. Prepare the files for installation by extracting the individual files from the PTF package, with the following command:
tar -xvf [file_path]dfs-3.1-aix61-P13.tar

Use the file path only if the PTF tar file is not in the current directory.
6. From the command prompt, enter smitty install to start the system management utility.
7. Select Install and Update Software.
8. Select Install Software
9. In the field labeled INPUT device/directory for software, type . to indicate the current directory or type the directory path where the PTF packages are stored.
10. The field labeled COMMIT must be set to NO if migrating to a HIGHER OS version, otherwise it can be set to YES.  For a complete explanation of migration scenarios, please click here.
11. Ensure that the fields labeled OVERWRITE same or newer versions? is set to yes.
12. Press Enter.
13. Restart the machine before starting DFS client or server. This step is required to force DFS to use new binaries.
Installing the DFS 3.1 PTF 13 on AIX 6.1(TL-02)
1.     Become the local superuser root (Single-user mode is recommended).
2. Stop all DCE and DFS processes on the machine.
3.     Ensure that you have PTF 12 installed on your machine.
4. Change to the directory where the PTF packages will be kept.
5. Prepare the files for installation by extracting the individual files from the PTF package, with the following command:
tar -xvf [file_path]dfs-3.1-aix61(TL-02)-P13.tar

Use the file path only if the PTF tar file is not in the current directory.
6. From the command prompt, enter smitty install to start the system management utility.
7. Select Install and Update Software.
8. Select Install Software
9. In the field labeled INPUT device/directory for software, type . to indicate the current directory or type the directory path where the PTF packages are stored.
10. Ensure that the fields labeled OVERWRITE same or newer versions? is set to NO.
11. Press Enter.
12. Restart the machine before starting DFS client or server. This step is required to force DFS to use new binaries.
Installing the PTF on AIX 5.3
1. Become the local superuser root (Single-user mode is recommended).
2. Stop all DCE and DFS processes on the machine.
3. Ensure that you have DFS 3.1 GA version and PTF 9 installed on system.
4. Change to the directory where the PTF packages will be kept. The AIX software delivery system allows downloading of individual fix packages or of the entire PTF.
5. If you have downloaded the entire PTF, prepare the files for installation by extracting the individual files from the PTF package, using one of the following command:

On AIX 5.3

tar -xvf [file_path]dfs-3.1-aix53-P13.tar

Use of file_path is required if the PTF tar file is not in the current directory.
6. From the command prompt, enter smitty install to start the system management utility.
7. Select Install and Update Software.
8. Select Update Installed Software to Latest Level (Update All). The Update Software by Fix (APAR) option also is supported. Refer to your operating system instructions for information on using this option.
9. In the field labeled INPUT device/directory for software, type to indicate the current directory or type the directory path where the PTF packages are stored.
10. The field labeled COMMIT must be set to NO if migrating to a HIGHER OS version; otherwise it can be set to YES.  For a complete explanation of migration scenarios, please click here .)
11. Ensure that the field labeled COMMIT software updates? is set to no and the field labeled SAVE replaced files? is set to yes.
12. Press Enter.
13. Restart the machine before starting DFS client or server. This step is required to force DFS to use new binaries.
Uninstalling the PTF
AIX Systems

The PTF software can be uninstalled by using the following method only if the field labeled COMMIT software updates? is set to no and the field labeled SAVE replaced files? is set to yes, as described above under Step 9. If the COMMIT option was set to yes during installation, the software cannot easily be uninstalled.

To uninstall the PTF on an AIX system, do the following:
1. Stop all DCE and DFS processes on the machine.
2. Become the local superuser root. (Single-user mode is recommended.)
3. From the command prompt, type smitty install
4. Select Software Maintenance and Utilities
5. Select Reject Applied Software Updates (Use Previous Version)
6. Select the software to uninstall.
7. Press Enter.
8. To start a DFS client or server using the reinstated software binaries, first restart the machine.

Note:

DFS PTF 12 is minimum DFS support levels for the AIX 6.1 and AIX 6.1(TL-02) operating systems.

DFS PTF 9 is minimum DFS support levels for the AIX 5.3 operating systems.

Therefore, uninstalling PTF 12 removes support for AIX 6.1 and AIX 6.1(TL-02), uninstalling PTF 9 remove support for AIX 5.3.

 



Contents of the PTF

 


Product notes

This section highlights general information and requirements that apply to this PTF release for IBM DFS 3.1 for AIX and Solaris.

To find the latest information about this product, please refer to the following IBM Web site:

http://www-306.ibm.com/software/stormgmt/dfs

Note:

This document does not duplicate the notes included in the README and Release Notes documents distributed with the general availability (GA) release of DFS 3.1, but those notes also apply to this PTF release unless otherwise specified. See those documents for additional information.

Support for Large Episode Aggregate

DFS 3.1 supports episode aggregate size only up to 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 up to 1TB size.

Support for DCE 3.2

DFS 3.1 for AIX and Solaris now supports DCE 3.2. A supported DCE product must be installed on the machine prior to installation of DFS 3.1.

Support for AIX 6.1 and 6.1(TL-02)

This PTF supports both 32-and 64-bit DFS 3.1 kernels on AIX 6.1. Refer to Using the PTF to enable AIX 6.1 and AIX 6.1(TL-02)support for information about installing DFS on AIX 6.1 and 6.1(TL-02) systems using the PTF release.

AIX 6.1 supports two types of local filesystems, JFS and JFS2. DFS currently supports only the JFS filesystem. This means that:

  • The filesystem containing the DFS cache must be a JFS filesystem.
  • Only JFS filesystems can be exported in DFS space.

Note: Currently DFS 3.1 does not support NFS Version 4 on AIX. DFS 3.1 also doesn’t work over Encrypted File System ( EFS ) on AIX6.1. It only works in conjunction with EFS enabled on the system.

Support for AIX 5.3

Starting from PTF 9, DFS supports both 32- and 64-bit DFS 3.1 kernels on AIX 5.3. Refer to the PTF 9 Readme for information about installing DFS on AIX 5.3 systems using the PTF 9 release. PTF 9 must exist on an AIX 5.3 system before later PTFs can be applied.

AIX 5.3 supports two types of local filesystems, JFS and JFS2. DFS currently supports only the JFS filesystem. This means that:

  • The filesystem containing the DFS cache must be a JFS filesystem.
  • Only JFS filesystems can be exported in DFS space.
Support for TSM 5.1 and TSM 5.2 on AIX

On AIX, DFS supports TSM 5.1 and TSM 5.2. Note that there is only one butc binary which can be used with both TSM 5.1 and TSM 5.2. To run butc on AIX, it is essential to have package

'tivoli.tsm.client.api.aix43.32bit' for TSM 5.1 and

'tivoli.tsm.client.api.32bit' for TSM 5.2

 installed in the system.

Migration tips

The following tips apply when upgrading DFS software to version 3.1 or installing a DFS 3.1 PTF.

Migration tips for AIX users
Using PTF 13 to enable AIX 6.1(TL-02) support
For DFS 3.1 support on AIX 6.1(TL-02), PTF 12 must be installed and should be followed by PTF 13. Before installing any later PTF's on AIX 6.1(TL-02), ensure that the General Availability (GA) version of DFS 3.1 was installed and that PTF 13 was installed with the overwrite option followed. Refer to section 'Using the PTF to enable AIX 6.1 and AIX 6.1(TL-02) support'
Using PTF 13 to enable AIX 6.1 support

For DFS 3.1 support on AIX 6.1, PTF 12 must be installed and should be followed by PTF 13. Before installing any later PTF's on AIX 6.1, ensure that the General Availability (GA) version of DFS 3.1 was installed and that PTF 13 was installed with the overwrite option. Refer to section 'Using the PTF to enable AIX 6.1 and AIX 6.1(TL-02) support' in this document for details.

Using PTF 9 to enable AIX 5.3

For DFS 3.1 support on AIX 5.3, PTF 9 must be installed. Before installing any later PTF's on AIX 5.3, ensure that the General Availability (GA) version of DFS 3.1 was installed and that PTF 9 was installed with the overwrite option.

DCE applications must be stopped before upgrade

Before upgrading to the Version 3.1 software or applying a DFS 3.1 PTF, all DCE applications must be shut down. To correctly upgrade an AIX-based machine, follow these steps:
1. Shut down all DCE applications, including DFS, and stop the DCE process.

Note:

The DFS Version 3.1 for AIX Quick Beginnings guide inappropriately recommends restarting the system as a means of shutting down DFS. This method will not be effective in most cases because DFS will automatically restart when the system restarts.
2. Install the DCE 3.1 software, including DCE 3.1 PTF 1 or install DCE 3.2
3. Install the DFS 3.1 software, including the DFS 3.1 PTF.
4. Start the DCE software. The start.dce command will trigger the migrate.dce command, which converts configuration files to the Version 3.1 format. If DFS was previously installed on the machine, the start.dce command also will trigger the migrate.dfs command.
5. Shut down and restart the machine.

Additional information about upgrading DCE and DFS software to Version 3.1 is available in the IBM Distributed Computing Environment for AIX Version 3.1 Quick Beginnings. (This Quick Beginnings document is available on the IBM Web site at http://www.ibm.com/software/network/dce/library/publications/dce31aix.html.) Information about installing a DFS 3.1 PTF is included earlier in this document, in Installing the PTF.

Restart after upgrade

To ensure proper function, restart AIX machines immediately after installing upgraded DFS software.

DCE PTF is required when using DCE 3.1

Before installing DFS Version 3.1 on an AIX  machine, ensure that a supported DCE is installed on the system. If you are using DCE 3.1, then DCE 3.1 PTF 1 is required.

If you received a CD containing DCE 3.1 and DCE 3.1 PTF 1, note that the PTF is supplied in the patches directory of the CD, and you must install the patch separately after installing the DCE software.

Online manual pages now available

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:

  • DFS Quick Beginnings
  • DFS Administration Guide
  • NFS/DFS Authenticating Gateway Guide and Reference
  • DFS Problem Determination Guide
Specifying a time interval between successive bak dump or bak dumpinfo commands

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.

Quick Beginnings gives incorrect filename for HTML documentation

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
Creating the root.dfs fileset

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."

System restart is inappropriate for stopping DFS

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.

Use "Install Latest" option to upgrade DFS 3.1 on AIX

When migrating AIX machines from IBM DCE DFS 2.2 to DFS 3.1 by using the SMIT or smitty utility, choose the Install Latest option to upgrade files. Choosing the Update All option does not properly update all the necessary files.

This note does not apply to the DFS 3.1 PTF installation procedures. Follow the instructions in Installing the PTF on an AIX machine to install a DFS 3.1 PTF.

Working around the "missing prerequisite" installation error

A code error in DFS 3.1 for AIX sometimes causes the installation program (SMIT or installp) to return an error message similar to the following:

missing prerequisite dce.client.runtime 3.1.0.125

This error has two possible causes. To determine which cause applies to your case, mount the CD-ROM and issue the following command:

grep 125 /cd mount point/usr/sys/inst.images/.toc

If no value is returned, you might be trying to install from a copy of the installation images that does not have a valid table of contents (.toc) file.

If the line *prereq dce.client.rte 03.01.0000.0125 is returned when you issue the grep command, you might have a defective CD-ROM that has an invalid table of contents (.toc) file.

To install DFS 3.1 from a copy of the installation images, copy the .toc file from the CD-ROM to the path where you copied the installation images. Using the inutoc command to create a .toc file after copying the installation images creates an invalid .toc file.

If the results of the grep command indicate that you might have a defective CD-ROM, check the part number. Proper disks have the part number CV6Z7ML printed on the front of the disk below the version number. Some preproduction disks with defective .toc files were accidentally released; these have the part number CV6F5ML. If you have a defective CD-ROM, contact your IBM sales representative for a replacement.



Defects fixed in this PTF

This section describes the updates to IBM DFS 3.1 for AIX  that are included in the service updates.

Defects fixed in PTF 13

A Reference APAR exists for each platform that supports PTF 13 for DFS 3.1. A Reference APAR provides a list of the APARs included in the platform's PTF.

·       APAR  IZ55646 (AIX 6.1)

·       APAR  IZ55729 (AIX 6.1(TL-02))

·       APAR  IZ55737 (AIX 5.3)

APAR IZ21950

DFS crashed when the zero list is full. Changes for the proper handling of the code EROFS are done.

This APAR contains the appropriate code changes to fix the performance problem.

APAR IZ55216

Illegal values in dfsstat output on 64 bit kernel because of a wrong data type.

The data type is changed from pkt_mutex to ulong32int64_t.

 Now dfsstat output is fine on 64 bit kernel OS.

This APAR contains the appropriate code changes to fix the performance problem.

APAR IZ55729

“cd to /:”  fails with permission denied error.

 DFS works fine with the changes done in kcred_setgroup kernel service- in TL2 of aix61.

 Initialize cr_groups to zero before calling kcred_setgroups.

This APAR contains the appropriate code changes to fix the performance problem.
Defects fixed in PTF 12

PTF 12 includes all updates that were in previous PTFs, plus the following items. PTF12 on AIX platform doesn’t include the fixes included in PTF11 platform.

A Reference APAR exists for each platform that supports PTF 12 for DFS 3.1. A Reference APAR provides a list of the APARs included in the platform's PTF.

  • APAR  IZ19525 (AIX 6.1)
  • APAR  IZ20961 (AIX 5.3)
  • APAR  IZ19527 (Solaris, update 4)

APAR IZ19642

DFS performance degrades on very large aggregates. This APAR contains the appropriate code changes to fix the performance problem.

Defects fixed in PTF 11

PTF 11 includes all updates that were in previous PTFs, plus bugs fixed for porting issues only 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. This PTF11 is only on Solaris 10 platform and not on any AIX platform.

Defects fixed in PTF 10

PTF 10 includes all updates that were in previous PTFs, plus the following items.

A Reference APAR exists for each platform that supports PTF 10 for DFS 3.1. A Reference APAR provides a list of the APARs included in the platform's PTF.

  • APAR  IY79285 (AIX 4.3.3)
  • APAR  IY79282 (AIX 5.1 and AIX 5.2)
  • APAR  IY79283 (AIX 5.3)
  • APAR  IY79284 (Solaris)

APAR IY75634

This allows user to set flserver thread count (VLSERVER_MAXNCSCALLS) by setting its value in environment variable.

APAR IY75635


" bosserver" core dumps, if we provide invalid admin list file as input to ' bos lsadmin' command.  The problem has been fixed.

APAR IY75637


DFS crashes system in function idl_free_krpc, as it tries to free a NULL pointer.  The problem has been fixed.

APAR IY61933


Error in setting and listing fileset quota greater than 4 TB. Now, "fts setq" command accepts any value(even >4TB) but actual fileset quota limit varies as per fragment size of the aggregate. The problem has been fixed.

APAR IY72864 (AIX 5.x)


DFS crashes AIX 5.x system running in debug mode. The problem has been fixed.

APAR IY74297


While working on a data from Linux NFS v2 client, NFS/DFS gateway server crashes intermittently. The problem has been fixed.

APAR IY78140

DFS crashes the system due to NULL value of key_info->refcnt. The problem has been fixed.

Defects fixed in PTF 9

PTF 9 includes all updates that were in previous PTFs, plus the following items.

A Reference APAR exists for each platform that supports PTF 9 for DFS 3.1. A Reference APAR provides a list of the APARs included in the platform's PTF.

  • APAR  IY67217 (AIX 5.3)
  • APAR  IY67216 (AIX 5.1 and AIX 5.2)
  • APAR  IY67214 (AIX 4.x)
  • APAR  IY67218 (Solaris)

APAR IY60271 (Solaris)

The DFS server machine panics as the default threadstack size on solaris 9 machines is falling short. The problem has been fixed.

APAR IY60523 (AIX 5.x)


On Aix 5.x DFS was causing machine crash in dmlfs. This change is relevant only to those customers, using the DFS Storage Management Toolkit. The problem has been fixed.

APAR IY60864 (AIX)


The current value of buffer cache is falling short for larger aggregates on heavily used file servers. The problem has been fixed.

APAR IY61062 (AIX 5.x)


On Aix 5.x, 64 bit mode, 'fts move' causes system crash for filesets which contains special device files. The problem has been fixed.

APAR IY63450


The fxd daemon is picking up out of range ports even after setting RPC_RESTRICTED_PORTS variable. The problem has been fixed.

APAR IY66881 (AIX)


The DFS memcache limit is increased to 128 MB from the existed 16 MB limit.

APAR IY68104 (AIX 5.x)

Access to DFS exported JFS file system fails with EACCES error. The problem has been fixed.

Defects fixed in PTF 8

PTF 8 includes all updates that were in previous PTFs, plus the following items.

A Reference APAR exists for each platform that supports PTF 8 for DFS 3.1. A Reference APAR provides a list of the APARs included in the platform's PTF.

  • APAR  IY56193 (AIX 4.x)
  • APAR  IY56196 (AIX 5.x)
  • APAR  IY56199 ( Solaris)
APAR IY45979

DFS client configuration fails when RPC_RESTRICTED_PORTS is set. This is when config scripts trying to change mode on links /:/ and /.:/ before their creation. Problem is fixed.

APAR IY47429

DFS client hangs in 'ls' command, due to a leak in dcache refcount. Problem is fixed.

APAR IY47430 (AIX 4.x and Solaris)

bosserver coredumps in 'bos lsadmin' command when used with an invalid adminlist file. Problem is fixed.

APAR IY47480

Due to un-initialized memory, machine panics while exporting an aggregate into DFS space. Problem is fixed.

APAR IY47512

DFS Client hangs when a thread tries to reacquire an scachelock. The deadlock has been fixed.

APAR IY47517 (AIX 4.x and Solaris)

'bak restoreft' command fails with the error "illegal host id". Problem is fixed.

APAR IY47518 (AIX 5.x only)

When a user belonging to more than 30 groups accessed DFS space, machine crashed. This problem is fixed.

APAR IY49491 (AIX 4.x and AIX 5.x)

Machine panics in rpc call due to improper VM handle on AIX POWER4 Processor. Problem is fixed.

APAR IY53458

'fts syncserv' output is not formatted properly when fldb entries are greater than or equal to 25. Problem is fixed.

APAR IY54966 (AIX 5.x only)

EFBIG error when uncompressing a file, resulting in the creation of a file larger than 4GB. Problem is fixed.

APAR IY56260

DFS 3.1 is now compatible with Tivoli Storage Manager (TSM) server release 5.2. The butc code in DFS 3.1 is recertified to support this new release.

Defects fixed in PTF 7

PTF 7 includes all updates that were in previous PTFs, plus the following items.

A Reference APAR exists for each platform that supports PTF 7 for DFS 3.1. A Reference APAR provides a list of the APARs included in the platform's PTF.

  • APAR IY45648 (AIX 4.x)
  • APAR IY45651 (AIX 5.x)
  • APAR IY45653 (Solaris)
APAR IY35651

Due to the file attribute synchronization problem in DM managed episode filesystem, UNIX sum command sometimes used to show wrong output. This problem has been fixed.

APAR IY38705

Repserver coredumps due to invalid connection pointer caused by wrong IP address. This problem has been fixed.

APAR IY38707

Repserver coredumps while trying to mark a fileset for deletion. This problem has been fixed.

APAR IY39503

The information about the locked filesets as shown by the fts fldb command is now being directed to stdout instead of stderr.

APAR IY42829

DFS Client machine crashed while trying to decommission FLDB machine from cell. This problem has been corrected.

APAR IY43512

In DFS Storage Management environment, changes made to files by DM applications were not visible to the DFS Clients. This problem has been fixed.

APAR IY44100 (AIX only)

The DFS Fileserver machine panics when client sends wrong packet. This problem has been fixed.

APAR IY44107

DFS 3.1 is now compatible with Tivoli Storage Manager (TSM) server release 5.1. The butc code in DFS 3.1 was recertified to support this new release. A single butc binary will now work with all the TSM versions.

APAR IY44421

DFS Fileserver used to panic while writing to a fileset having an exceeded disk space or fileset quota. This problem has been resolved to return appropriate error codes.

APAR IY44422

The time field for the read-only copy of a fileset was not initialized by the fileserver. This stopped DFS clients from accessing the fileset. This problem has been fixed.

Defects fixed in PTF 6

PTF 6 includes all updates that were in previous PTFs, plus the following items.

A Reference APAR exists for each platform that supports PTF 6 for DFS 3.1. A Reference APAR provides a list of the APARs included in the platform's PTF.

  • APAR IY40011 (AIX 4.x)
  • APAR IY40013 (AIX 5.1)
  • APAR IY40010 (Solaris)
APAR IY33061 (AIX 5.1 only)

dfsiauth command now show authentication mappings on AIX 51 machine in 64 bit mode.

APAR IY33523 (AIX only)

Credential files generated by "list" and "delete" option of dfsiauth command were not purged after these commands completed execution. This problem has been fixed.

APAR IY34041 (AIX only)

dfsiauth command will now show complete hostname.

APAR IY34159

System performance decreases while copying files in DFS space after increasing the cache size beyond 2.6 GB. This problem is now corrected.

APAR IY34162 (Solaris only)

On a mutlitple CPU sparc machine running Solaris 8, "cd" to dfs space hangs while accessing the rootvnode of the dfs filesystem. This problem has now been fixed.

APAR IY34327 (Solaris only)/IY34328 (AIX only)

The DFS cache manager was returning the error code of the parent directory, instead the file being looked upon. The code has been modified so that the DFS cache manager will return the correct error code to the user.

APAR IY35648 (AIX 5.1 only)

On an AIX 51, 64 bit kernel, the "df/mount" command stops working if any of the episode fileset is mounted locally. This problem is now corrected.

APAR IY35720 (AIX 5.1 only)

DFS server crashes on AIX5.1 machine, while doing any operation in a local file system which is exported through DFS. This problem has been fixed.

APAR IY35832

When new server entry name is part of already entered server name , then 'bak addftentry' command erroneously returns with duplicate server entry. The problem has been fixed.

APAR IY36649

Configuring dce with "autostart" and "clean_autostart" option and then configuring dfs with "autostart" option used to cause dce services to fail at startup. This problem has been corrected.

APAR IY36650

Stop.dfs sometimes fails to stop running upclient process. This problem has been corrected.

APAR IY36651

On a machine with dce hostname different from the machine local host name, dfsexport used to fail while detaching aggregate. This problem has been fixed.

APAR IY37347

If we run dfsstat on a Solaris 7/8 DFS 3.1 PTF5 client machine, it tries to retrieve File Server thread pool values and fails. This problem has been fixed.

APAR IY37420 (AIX only)

The dcecp is unable to handle multi piped commands particularly on faster machines. This led to a problem while trying to configure DFS servers. The problem has been fixed.

APAR IY37751

Modification of a fragmented file in episode filesystem causes crash on AIX and solaris m/c in 64 bit mode. This problem is fixed.

APAR IY38198

After changing the IP address of any fileserver machine, DFS client is unable to access any of the fileset residing on that server for few minutes resulting in an error. This problem is now being fixed.

APAR IY38258

DFS client machine hangs due to a deadlock between threads. The problem has been fixed.

APAR IY38260

DFS client machine panics due to a deadlock in the cache manager code. The problem has been fixed.

APAR IY38266

asciiview program in IDFSenUSd package has been renamed to asciiview.dfs, due to a conflict with the same binary name in DCE docs package. Users can access the program with the renamed version.

APAR IY38267

While running many concurrent fts dump commands, some of those dump command fail with the error EBADF. This is due to the volume descriptor getting garbage collected incorrectly before completion of operation on that volume. The problem has been fixed.

APAR IY38405 (Solaris only)

DFS3.1 has now been recertified to work on Solaris 9.

APAR IY38443 (AIX 5.1 only)

Machine crashed while handling rpc exception on AIX 51 machine in 64 bit mode. This problem has been fixed.

Defects fixed in PTF 5

PTF 5 includes all updates that were in previous PTFs, plus the following items.

A Reference APAR exists for each platform that supports PTF 5 for DFS 3.1. A Reference APAR provides a list of the APARs included in the platform's PTF.

  • APAR IY33232 (AIX 4.x)
  • APAR IY33233 (AIX 5.1)
  • APAR IY33234 (Solaris)
APAR IY28852 (AIX only)

When the RPC_RESTRICTED_PORTS environment variable was set, the message that was logged in the cfgdce.log file was incorrectly interpreted as an error message. The message is now correctly interpreted as an informative entry indicating that ports are restricted to a given range.

APAR IY29795

When a replicated fileset is renamed and mount point re-evaluated from one client box,   "cm whereis ." command  returns the old fileset name for the new read-only mount-point,  if run from the same client. This problem has been fixed.

APAR IY30379 (Solaris only)

DFS client machine panicked when setting a pag for a user. The panic occured while attempting to release an already-released mutex. This problem has now been corrected.

APAR IY30498

Reconfiguring fileserver on a machine sometimes resulted in an orphaned UUID in the bosserver administrative list. The problem has been corrected.

APAR IY30542 (AIX only)

The dfsstat tool is now available on both 32-bit and 64-bit environment for AIX 5.1 systems.

APAR IY30836

Repeated starting or stopping of DCE/DFS causes the dcecp program to coredump. This problem was due to memory reference being freed by both DCE and DFS code. The problem has been fixed.

APAR IY30841 (AIX only)

In the binary distribution process from upserver to upclient, file attributes were not being properly transferred from server to client. This problem occurred because of a change in the variable name used for file size in the stat structure for AIX. The problem has been corrected.

APAR IY31492 (Solaris only)

DFS Fileserver service threads caused a system hang, while trying to process a who-are-you challenge validation. This problem was due to solaris kernel not supporting time sliced preemption of SYS class threads. If such a thread is looping around a code path, that would result in a CPU starvation for other threads waiting for a CPU cycle, resulting in a hang. This problem has been fixed.

APAR IY31532

dfsstat command has been enhanced to display the following values from the  
Fileserver threadpools represented by the fxd's mainprocs and tokenprocs parameters :-

  • Number of RPC calls currently queued,
  • Maximum number of RPC calls supported by the thread pool queue.
APAR IY31729 (Solaris only)

Executing dfsstat binary would now invoke the appropriate 32-bit or 64-bit binary in respective environment.

APAR IY31791

DFS access failures were encountered when client sets the machine context with the Fileserver and receives an EINTR error code. This happened because cache manager did not handle the return code properly, and erroneously used to mark the server down. This code is now handled correctly.

APAR IY31897 (AIX only)

When configuring the DFS client on an AIX 5.1 system on which the cache directory does not reside in the JFS file system, the DFS client took more than two minutes to display a failure message. Now, in this circumstance, an error message is reported immediately.

APAR IY31999

When a fileset is created by a DCE principal of a foreign cell, the owner of the fileset was set to foreign DCE principal creating it. This has been modified to set the fileset owner as local root.

APAR IY32041 (AIX only)

Garbage collection, a feature in NFS-DFS gateway, which periodically deletes unauthenticated and expired mappings from the gateway machine, has been enhanced to run according to user specified parameters. Note that the garbage collector runs once the total number of mappings ( mapping threshold ) exceeds a specific limit. Two new command-line options have been added to the "dfsiauth" command suite :-

  • dfsiauth -modifygc [ -g time_diff -n mapping_threshold ] enables user to set the frequency ( time_dff in minutes) at which the garbage collector would run. It could also be used to set the mapping threshold, which, once reached, causes garbage collection to take place after each time_diff minute.
  • dfsiauth -viewgc enables users to retrieve the values of "mapping threshold" and "garbage collection interval" from the kernel.
APAR IY32053

On a machine running DCE 3.2 components and having DFS components installed or configured, restarting the following DCE components failed: gdad, dts client, dts global, audit, ems, password strength server. The problem has been identified and corrected.

APAR IY32087 (Solaris only)

DFS client machine panicked when trying to display an error message. The panic occured while attempting to release an already-released mutex. This problem has now been corrected.

APAR IY32139

Performing a store operation on a fileset having an exceeded disk quota sometimes caused the DFS machine to panic. This problem has been fixed to return an error message and the machine does not panic.

APAR IY32151

Following command line options have been introduced in "cm" command suite to activate or deactivate the DFS cache manager bulkstat feature from a client machine at runtime :

  • cm getbulkstat : It reports the whether the bulkstat feature in enabled or disabled.
  • cm setbulkstat : It enables or disables the bulkstat feature.  By default, this feature is enabled on all client machines.

The bulkstat feature provided by cache manager collects bulk data to be added to the caches for the names and statuses of files in a directory on which a lookup is to be made. This happens only if the directory lookup is being made for the first time.

Note : We have added this cm bulkstat feature in the belief that it may improve performance for some customers depending on their specific data access patterns. However, please note that the messages for this new feature have not been translated to any languague other than English.

APAR IY32158 (Solaris only)

Users were experiencing DFS access failures sporadically due to the self credentials being marked as expired by DFS Cache Manager. This problem has been corrected.

APAR IY32164

If a parent directory is having more than 65533 sub-directories, then removing one of those sub-directories panics the machine. The linkcount of parent directory overflows when there are more than 65533 sub-directories. This problem has been corrected by putting a check on the linkcount of the parent directory. Now, creation of a new sub-directory in a parent directory , already having 65533 sub-directories, fail with error EMLINK.

APAR IY32256 (AIX only)

On AIX 5.1 systems, the value of the SYS_NAME parameter has been modified. Now, rs_aix51 is returned when the cm sysname command is issued.

Defects fixed in PTF 4

PTF 4 includes all updates that were in previous PTFs, plus the following items.

A Reference APAR exists for each platform that supports PTF 4 for DFS 3.1. A Reference APAR provides a list of the APARs included in the platform's PTF.

  • APAR IY30096 (AIX 5.1)
  • APAR IY30093 (AIX 4.x)
  • APAR IY29985 (Solaris)
APAR IY23586 (Solaris only)

After restarting a DFS Client machine, the command start.dce all failed to start the DFS client and returned the following error message.

dfsd: failed to invoke the TKN server (code 22)

The problem has been identified and corrected.

APAR IY24312 (AIX only)

When using the SMIT or smitty utility, the following DFS Fileset Replication Server operations did not function:

  • Unconfigure DCE/DFS
  • Stop DCE/DFS Components
  • Restart DCE/DFS Components

This occurred because the operational name of the DFS Fileset Replication Server component is dfs_repsvr; however, the name of the component being used by the smitty utility was dfs_rep_svr. This inconsistency has been fixed and the smitty utility can now be used for DFS Fileset Replication Server operations.

APAR IY24436 (Solaris only)

Numerous unnecessary messages were returned when a user attempts to start DCE on a Solaris 7 or Solaris 8 machine on which DFS 3.1 is installed but not configured. The unnecessary messages are no longer displayed.

APAR IY24534 (Solaris only)

A Solaris 8 system panicked due to a message ID mismatch. Now, the correct message IDs are generated and the problem has been corrected.

APAR IY24868 (AIX only)

Users were sometimes unable to transfer files to DFS space using FTP after upgrading to AIX ML09. This problem has been corrected.

APAR IY24869 (AIX only)

Users sometimes received no response when performing directory operations, such as ls, in the DFS filespace. The DFS buffer cache implementation has been modified to correct this problem.

APAR IY26163

Previously, online manual pages were not available with DFS 3.1. The dfsman utility has been created and can now be used to access DFS manual pages. See Online manual pages now available for details.

APAR IY26675 (AIX) and APAR IY26676 (Solaris)

When a cloned fileset's quota limit was exceeded, delete operations were not permitted. This problem has been identified and corrected.

APAR IY26923

The DFS 3.1 client sometimes failed due to a null pointer. A conventional check for a null pointer has now been introduced in the client code and the failure no longer occurs.

APAR IY27007

DFS file server configuration failed when replica security servers were out of sync with the master server. The problem has been identified and corrected.

APAR IY27012

In a DCE cell with replicated security servers, attempting to unconfigure a DFS file server machine sometimes resulted in an incomplete unconfiguration. This problem has been identified and corrected.

APAR IY27015

Previously, when configuring the DFS client to use a memory cache with a size greater than 64 MB, the DFS client failed and returned an incorrectly formatted and misleading error message. The following changes have been made to resolve this problem.

  • For Solaris, the memory cache size constraint of 64 MB has been removed.
  • For AIX, in the configuration script, the memory cache size maximum has been changed to 16 MB for consistency with the internal DFS code.
  • If a failure occurs due to memory cache settings, the correct error message is returned.
APAR IY27153

The DFS code has been modified so that the ftserver extracts the DCE principal and group from the binding handle and passes it through the volume status structures, ensuring that the DCE principal that created the fileset is the owner of the fileset.

APAR IY27192 (Solaris only)

A Solaris 8 system panicked when the dfsgw add command was executed. This problem has been corrected.

APAR IY27489

The DFS configuration script incorrectly disallowed the creation of a DFS client cache greater than 1.5 GB. The DFS client cache limit is now correctly calculated based on the chunk size setting, specifically 32000 * chunk size.

APAR IY27582

The dfsstat tool for collecting and analyzing performance data is now available with DFS 3.1 on Solaris and AIX 4.x systems. This tool can be used to gather various file server, Cache Manager, and RPC statistics. For Solaris, there are both 32-bit and 64-bit versions of the tool available in the /opt/dcelocal/bin and /opt/dcelocal/bin/sparcv9 directories, respectively.

APAR IY27583 (Solaris only)

The environment variables RPC_UNSUPPORTED_NETIFS and RPC_UNSUPPORTED_NETADDRS were being ignored. This occurred because the DFS variables created to hold the values of these environment variables were being incorrectly set to NULL instead of the environment variables' values. The problem has been corrected and the environment variables now function correctly to block a network interface or an IP address from being picked up by the File Exporter daemon.

APAR IY27589

When executing the bos lsadmin command, the boserver failed and wrote to a core file. A memory leak in the BOSSVR_ListSUsers function was found and corrected.

APAR IY27593 (AIX only)

An AIX 4.3.3 system running as an NFS/DFS Authenticating Gateway sometimes failed. This occurred because DFS code was using a field that the NFS code now uses. The problem has been corrected and the failure no longer occurs.

APAR IY27851

DFS 3.1 is now compatible with Tivoli Storage Manager (TSM) server release 4.2. The butc code in DFS 3.1 was recertified to support this new release. For AIX 4.x and for Solaris, versions of butc corresponding to TSM 3.7, TSM 4.1, and TSM 4.2 are being delivered. For AIX 4.x, select the appropriate butc version by changing the link from /usr/bin/butc to /usr/lpp/dce/bin/<butc37 | butc41 | butc42>. For Solaris, select the appropriate butc version by changing the link from /usr/bin/butc to /opt/dcelocal/bin/<butc37 | butc41 | butc42>. For AIX 5.1, only butc42 is being delivered because only TSM 4.2 is supported.

APAR IY27965

Documentation does not exist to assist users in determining an appropriate minimum time limit between successive bak dump or bak dumpinfo commands. If bak dump or bak dumpinfo commands are executed too closely in succession, errors may result. See Specifying a time interval between successive bak dump or bak dumpinfo commands for more information.

APAR IY28246

In a cell with a System Control server, unconfiguration of the DFS file server using the -config_type value admin left stale entries in the admin.up and admin.ft files. These stale entries corresponded to the already deleted server principal UUIDs during the unconfiguration process. This problem has been corrected.

APAR IY28249

Changes were made to the DFS 3.1 configuration scripts to support successful configuration of DFS 3.1 on both DCE 3.1 and DCE 3.2.

APAR IY28304 (AIX only)

The DFS client had a leak in the vnode reference count, which caused several resource problems. For example, deleting a tarred file while the tar process was running did not free space on the fileset, even if the tar was killed. The leak has been repaired and the resource problems no longer occur.

APAR IY28340

The DFS flserver stopped receiving read requests and generated errors for an unapparent reason. This was due to the error handling in Ubik transaction commit processing that was not allowing the freeing of internal resources, leading to an exhausted resource pool and the blockage of normal processing. Ubik error handling has been corrected and internal resources are now properly freed.

APAR IY28432 (Solaris only)

It was possible to experience sporadic DFS Client access failures. This occurred when the client made a call to either the file server or the replication server because the self credentials were not being refreshed. Now, the self credentials are being properly refreshed and access failures are no longer experienced.

APAR IY28543

An incorrect address count was being reported in fshost trace messages because an internal count was not being updated consistently. The count maintenance has been repaired.

APAR IY28887 (Solaris only)

If RPC variables were not specified in the list of exported variables in the /etc/default/init file, then the DFS file server fxd process did not pick up the information. Now, when the RPC variables are not specified in the environment, the dfsbind process reads the /opt/dcelocal/etc/environment file and passes the RPC variable information to the fxd process.

Defects fixed in PTF 3

PTF 3 includes all updates that were in PTF 1 and in PTF 2, plus the following items.

A Reference APAR exists for each platform that supports PTF 3 for DFS 3.1. A Reference APAR provides a list of the APARs included in the platform's PTF.

  • APAR IY25980 (AIX 5.1)
  • APAR IY24032 (AIX 4.x)
  • APAR IY24036 (Solaris)
APAR IY15453

The system sometimes stopped responding while running some set attribute calls on DB2 datalinks, because the changes were not being flagged properly. Code changes were made in the DFS Cache manager functions to check for the setAttr flag when storing modified information for a file.

APAR IY19598

The fts lsfldb command did not work properly on detached aggregates, using the aggregate name or id to list filesets. This problem has been corrected so that the aggregate id may be used.

APAR IY20056

The DFS 3.1 configuration script displayed the following spurious error message:

0x113152c8: The value, admin, is not recognized for the keyword, config_type.

This problem has been corrected.

APAR IY20125 (Solaris only)

The DFS 3.1 server panicked when trying to write to a DM-managed aggregate on a 64-bit Solaris platform. This problem has been corrected.

APAR IY20260 (Solaris only)

A Solaris 64-bit platform panicked while trying to write to a DM-managed aggregate, because it attempted to release a mutex lock before it was obtained. This problem has been corrected.

APAR IY20275 (AIX only)

This is an enhancement to the unsupported component dfsstat, which will be made available with PTF 3. The dfstat program collects various Remote Procedure Call (RPC) and DFS statistics that may be useful in performance analysis, load monitoring, or environment characterization. This program has been further enhanced to display the tokenprocs and mainprocs thread counts (total and idle) of the DFS fileserver process called fxd.

APAR IY20294

DFS 3.1 is now compatible with Tivoli Storage Manager (TSM) server releases 3.7 and 4.1, and TSM client releases 3.7.1, 3.7.2, 4.1.1, and 4.1.2. The butc code in DFS 3.1 was recertified to support these new releases.

APAR IY21026

The fts addsitefileset server_name aggregate2 command returned an incorrect error message as follows:

Cannot create another R/O replica on server name (aggregate1)
There is already one on server name (aggregate1)

In this error message, the first aggregate name listed (aggregate1) should display as (aggregate2). This has been corrected.

APAR IY21902 (Solaris only)

On Solaris systems with 64-bit kernel, the DFS 3.1 server sometimes panicked while trying to write to a DM-managed aggregate. The problem resulted from trying to store the 64-bit structure address in a 32-bit thread id in DM. The problem has been corrected and 64-bit values are now properly ported.

APAR IY21903 (Solaris only)

On Solaris systems with 64-bit kernel, a call to the dm_path_to_fshandle API on an exported DM-managed aggregate returned an ENODEV error (which translates to "No such device"). This problem occurred in a 64-bit environment because the device number in the aggregate was specified as a 32-bit integer. This defect has been fixed.

APAR IY21981 (Solaris only)

On Solaris, a core dump sometimes resulted when unmounting the dmlfs aggregate. The problem was resolved by adding a new field, freevfs, to the DM vfs operations, to prevent accessing the wrong pointer while doing the unmount.

APAR IY22481

The DFS client crashed when the DFS Cache Manager attempted to release a write lock before it was obtained. The code was modified so that the lock is obtained before the call to release it is made.

APAR IY22482

During automatic tape backups, the wrong date was entered in the DFS central log. The butc code was modified to fix this problem.

APAR IY22706 (AIX only)

When using the smitty utility for unconfigure, restart, and stop operations for all components, these operations were carried out on DCE components only, and not on DFS components. This problem occurred only on systems with DFS 3.1 PTF 1 and above. These operations now function correctly.

APAR IY22820

The dfsexport function was unable to detach the dmlfs aggregate when the -force flag was specified. The solution involved code modifications to check for force flags in addition to other conditions.

APAR IY22825 (AIX only)

The smitty utility did not display the correct id for a new aggregate. Instead, it passed the value equal to the one following the highest used aggregate id. The logic was changed to generate the correct default value as the first unused id.

APAR IY22971

If a df command was issued when DCE was already running, some of the DFS filesystem entries were displayed two or more times. This problem occurred if the number of aggregates was more than 24. To fix it, the allowable number of aggregates was increased.

APAR IY23000

The DFS backup process failed because a function call from the butc command erroneously returned loopback as the host name, and there is no matching entry in the database. The code was changed to return the correct host name.

APAR IY23012 (Solaris only)

The need for the en_US locale on Solaris was not documented. Users should be aware that DFS 3.1 on Solaris 7 and 8 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."

APAR IY23018

A server panic prevented users from accessing DFS space when the authentication level was set to pkt_privacy. The code was modified to correct this problem.

APAR IY23182

The replica server core dumped when trying to set the delete flag for a volume that was already marked for deletion. This problem was caused by an inconsistency between the Fileset Location Database (FLDB) and the local replica information. The problem was corrected by providing an extra conditional check for the delete flag.

Defects fixed in PTF 2

PTF 2 includes all updates that were in PTF 1, plus the following items.

A Reference APAR exists for each platform that supports PTF 2 for DFS 3.1. A Reference APAR provides a list of the APARs included in the platform's PTF.

  • APAR IY19669 (AIX)
  • APAR IY19672 (Solaris)
APAR IY15168

When a non-local user was added to a local group, the user was not automatically assigned all the group's permissions. This problem has been corrected.

APAR IY15347

In the GA software, processes controlled by the BOS (basic overseer) server all started from the same path, /opt/dcelocal/var/dfs/adm, and all wrote core files in that path if they failed. To distinguish the core files, the BOS server renamed the files to core.process_name after they were written. It was possible for core files to be corrupted if more than one process created a core file at the same time because the BOS server process was not able to complete the renaming. In this situation, the BOS server sometimes gave an error message like the following: Core file program (ftserver) does not match current program (core ignored).

This change causes the BOS server to start each process from a different path corresponding to its process name. If a process writes a core file, that file will be named core and stored in the process-specific directory. A symbolic link will be created in the /opt/dcelocal/var/dfs/adm/ path with the old-style name, core.process_name.

For example, a BOS server-controlled process that is named ftserver will be started with the path /opt/dcelocal/var/dfs/adm/ftserver. If it fails and writes a core file, the file will be /opt/dcelocal/var/dfs/adm/ftserver/core. A symbolic link to the core file will be created as /opt/dcelocal/var/dfs/adm/core.ftserver.

APAR IY17447

It was possible for the cache manager of a DFS client machine to classify a file server as nonfunctional (down) because of user authentication failures at the file server machine. This behavior has been eliminated.

APAR IY17937 (Solaris only)

DFS servers on Solaris systems sometimes panicked during a backup operation while trying to fetch directory status as a bulk operation. While trying to fetch directory status, a function attempted to release a preemption lock that already had been released; the error message mutex_exit: not owner resulted. This problem has been corrected.

APAR IY19103 (Solaris only)

DFS failed to start on Solaris machines after the Solaris 7 operating system kernel patch 106541-14 had been applied. The Solaris patch overwrites a system file, /etc/name_to_sysnum, which contains a DFS-related entry. DFS now checks for the required entry at initialization and writes the appropriate value if it does not exist. For additional information about /etc/name_to_sysnum, refer to Using a PTF to enable Solaris 8 support.

APAR IY19186

Setting the environment variable RPC_UNSUPPORTED_NETADDRS on a DFS file server after configuring DCE and DFS sometimes caused DFS clients accessing the file server machine to crash. Modifying the environment variable changed the flserver binding information in the cell directory service, and client dfsbind queries returned an unacceptable value. This problem has been corrected.

APAR IY19485 (Solaris 8 only)

The Solaris 7 versions of two binaries, epimount and epiunmount, were included in the Solaris 8 installation of PTF 1. The code did not function correctly in a Solaris 8 environment. The correct versions of these binaries are supplied in PTF 2.

APAR IY19487 (Solaris only)

It was possible for data on a Solaris DFS 3.1 file server to be corrupted by a write operation from an IBM DFS for Windows Version 3.0 client. The problem was caused by an unacceptable value that was passed to the Solaris machine with a buffer file. The file server now checks the value before passing it to the Solaris routine.

APAR IY20017

A runtime error sometimes occurred when an IBM DFS client attempted to store data on a DFS server. The error occurred because the server attempted to change a transmission setting that the client was unable to change. The server code no longer attempts to renegotiate that setting for the duration of communication with the client.

Defects fixed in PTF 1

The following updates were included in PTF 1. They also are included in PTF 2.

A Reference APAR exists for each platform that supports PTF 1 for DFS 3.1. A Reference APAR provides a list of the APARs included in the platform's PTF.

  • APAR IY16728 (AIX)
  • APAR IY16729 (Solaris)
APAR IW00494 (AIX only)

This change eliminates a synchronization error that sometimes caused a system failure on AIX machines.

APAR IY07929

Detaching a DM (data management) aggregate caused a system failure when the aggregate had events pending. The abandon_Seq() procedure is rewritten to send a CANCEL command for pending events when the related aggregate is detached.

This change is relevant only to those customers using the DFS Storage Management Toolkit.

APAR IY09122 (Solaris only)

An error caused a failure in the DFS core process when an incorrect encryption key was received from a DFS client during a remote procedure call (RPC). This problem has been corrected.

APAR IY11036

The flserver command, which is used to instantiate fileset servers, failed because of a code error. This error has been eliminated.

APAR IY12153 (AIX only)

An incorrectly set buffer pointer in an internal function caused a DFS server failure. The problem has been fixed.

APAR IY12788

In the previous code release, it was possible for the fts release command to fail to complete when the -wait option was used and a remote procedure call (RPC) failed. This problem has been remedied.

APAR IY12890

The maximum size of the volume descriptors table maintained by the DFS kernel has been increased from 50 to 250 entries.

APAR IY13058

This change allows administrators to disable Fileset Location Database (FLDB) locking for replication server updates.

Normally, a replication server locks the FLDB entry for a fileset before loading updates from that fileset, and unlocks it when finished. Locking the FLDB entry makes the fileset unavailable to other administrative operations until the replication server has finished retrieving updates. Greater speed can be achieved if the FLDB entry is not locked during replication, but the replication server can possibly interfere with other administrative actions on that fileset if the FLDB entry is not locked. Consider the possible risks before using this option.

The repserver command now recognizes the option -unlocked. If this option is used, the replication server does not lock the FLDB entry while performing updates.

APAR IY13316

The fts move command sometimes failed for large filesets (60 GB or more) because a code error allowed the ftserver garbage collection process to delete the transaction identifier before the original fileset was completely removed. This problem has been corrected.

APAR IY13563 (AIX only)

The code that interacts with VMM (virtual memory manager) functions in AIX has been modified to provide more information for debugging purposes.

APAR IY13566 (AIX only)

A code error sometimes caused multiprocessor DFS client machines to stop responding. The problem, which occurred only on the AIX operating system, has been corrected.

APAR IY13973 (AIX only)

An incorrect call to the AIX system function naix_create_attr() caused a server panic. This problem has been eliminated.

APAR IY14065 (AIX only)

Spurious error messages, indicating that the DFS file server component had not started, appeared when DFS was started and the RPC_RESTRICTED_PORTS environment variable was set. The erroneous messages follow.

Unable to start DFS file server
The components on DFS host did not start correctly

This behavior has been eliminated.

APAR IY14141 (AIX only)

An omitted header file caused migration from DFS Version 2.1 to DFS Version 3.1 to fail. This problem has been corrected.

APAR IY14535 (AIX only)

An uninitialized variable sometimes caused a system failure when Episode vnodes were accessed. The variable is now initialized when the system starts.

APAR IY14667 (AIX only)

SMIT panels for configuring the DFS client were missing. The DFS client configuration options now appear on the Configure, Unconfigure, Stop, and Restart panels.

Additionally, an error that prevented fileset mount points from being deleted when the SMIT panel was used for this task has been corrected.

APAR IY14689

A code error sometimes caused a server panic when DFS servers with class B or class C Internet protocol (IP) addresses attempted to access the DFS file space. This problem has been corrected.

A class B IP address is one in which the first and second fields are fixed values assigned by Internet authorities. A class C IP address has its first three fields assigned by Internet authorities. For example, a company with a class B IP address might use IP addresses of the form 130.0.*.*, where * represents any number between 0 and 255.

This problem did not affect servers with class A IP addresses, in which only the first field contains a fixed value.

APAR IY15335

A system panic resulted when a nonroot process attempted to set its DFS authentication credential to one not owned by that process. For example, this might happen if a Web server process received a user name and password and attempted to use that credential to access DFS filespace. The problem has been eliminated.

APAR IY15337

A discrepancy between the response packet size expected by user-available functions and the size expected by kernel functions sometimes caused functions in the dm_ group to fail with the error code EFBIG. This problem has been eliminated.

This change is relevant only to those customers using the DFS Storage Management Toolkit.

APAR IY15445

It was possible for a null pointer to be dereferenced during execution of the dmepi_set_acl function, causing a system panic. This problem has been eliminated.

This change is relevant only to those customers using the DFS Storage Management Toolkit.

APAR IY15446

The dmepi_set_acl function worked incorrectly when used to modify a directory's initial object access control list (ACL). The function incorrectly modified the directory's initial container ACL instead of its initial object ACL. This error has been corrected.

This change is relevant only to those customers using the DFS Storage Management Toolkit.

APAR IY15447

The cfgdmepi system function failed to load the kernel extension dmlfs.ext because of an uninitialized variable. This problem has been eliminated.

This change is relevant only to those customers using the DFS Storage Management Toolkit.

APAR IY15454

The -noautoquery option in the backup tape coordinator (butc) command did not work as specified. The tape coordinator process prompted the administrator to mount the first tape regardless of whether the -noautoquery option was used. This error has been corrected.

APAR IY15466 (AIX only)

A code error allowed the dfsd process to return the message that dfsd had started successfully before cache initialization was complete. The process now waits for confirmation that the cache is initialized before issuing the success message.

APAR IY15903 (Solaris only)

The dfsexport -detach command failed undetectably because of a corrupted value in the agfs_fstype field of the fileset identifier (fsid). This problem has been eliminated.

APAR IY15919

Attempting a chmod() action that was forbidden by a data management (DM) application on the server caused the cache manager to emit a continuous sequence of AFS_StoreStatus remote procedure calls until the client was restarted. This problem has been eliminated.

This change is relevant only to those customers using the DFS Storage Management Toolkit.

APAR IY15920

The rmdir command failed without giving an error message when executed on a nonempty DFS directory. The command now returns the error code ENOTEMPTY in this case.

APAR IY15932

It was possible to overflow the allotted storage space for reference count values in the cm_volume.c file by setting the allowed number of status cache entries in the DFS cache manager to a value greater than 30,000. (The number of status cache entries in the DFS cache manager is configured by using the dfsd -stat command option.) A server panic, documented by a failed assertion message, resulted from the overflow.

Additional storage space has been allotted for the reference count variable to correct this problem.

APAR IY15982

An error prevented the links agfs, lfs, and dmlfs from being created in the /usr/lib/fs/ path during installation. This error has been eliminated.

APAR IY16329 (Solaris only)

A programming error allowed a data management lock structure to be referenced after its destruction if a kernel module removal function failed. A system panic resulted in Solaris systems. This error has been eliminated.

APAR IY16349 (Solaris only)

A system panic occurred in 64-bit Solaris systems during removal of a file from a type DMLFS aggregate. The problem occurred because of a recursive procedure call, which has been eliminated.

APAR IY16561 (AIX only)

The default location for the DFS client cache on AIX systems was erroneously set as /var/adm/dfs/cache. The default location now is set to the correct value, which is /var/dce/adm/dfs/cache.

APAR IY16563 (Solaris only)

Migrating files from a DM-managed aggregate failed on 64-bit Solaris systems, with an EFAULT error code being returned from the DMAPI calls dm_read_invis() or dm_write_invis(). This problem has been eliminated.

This change is relevant only to those customers using the DFS Storage Management Toolkit.

APAR IY16626 (Solaris only)

A code error caused the dm_get_bulkattr() function to return incorrect status information on DM-managed aggregates. This problem, which occurred only on Solaris systems, has been eliminated.

This change is relevant only to those customers using the DFS Storage Management Toolkit.





(c)
IBM Corporation 2001-2009. All Rights Reserved

Rate this page:

(0 users)Average rating

Document information


More support for:

DFS

Software version:

3.1

Operating system(s):

AIX

Software edition:

All Editions

Reference #:

1417117

Modified date:

2010-01-07

Translate my page

Machine Translation

Content navigation