Version 3.6
First Edition (January 2002)
This edition applies to:
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.
(C) Copyright International Business Machines Corporation 2000, 2001, 2002. All rights reserved.
U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This file documents the fixed defects and remaining limitations associated with the Patch 4 release of AFS(R) 3.6 (build level afs3.6 2.32).
This document has the following sections:
For UNIX systems, you use the same procedure to install a patch distribution as to upgrade from a previous release. See the upgrade instructions in the AFS Release Notes.
For Windows systems, patches can be installed directly to the base 3.6 product or over any previous patches. The AFS for Windows installation program displays a series of dialog boxes that lead you through the installation process. Follow the directions in each dialog box and select the appropriate options.
AFS 3.6 Patch 4 supports the following system types.
| alpha_dux40 | DEC AXP system with one or more processors running Digital UNIX 4.0f |
| alpha_dux51 | DEC AXP system with one or more processors running Compaq Tru64 5.1 or 5.1a |
| hp_ux110 | PA-RISC-based Hewlett-Packard system with one or more 32- or 64-bit processors running HP-UX 11.0 |
| hp_ux11i | PA-RISC-based Hewlett-Packard system with one or more 32- or 64-bit processors running HP-UX 11i |
| i386_linux24 | IBM-compatible PC with one or more processors running RedHat Linux 7.1 with kernels: 2.4.2-2, 2.4.3-12 |
| i386_nt40 | IBM-compatible PC with one or more processors running Microsoft Windows 2000 or NT 4.0 with Service Pack 4, Service Pack 5, or Service Pack 6; Light Client functionality only is supported for machines running Windows 95 with Windows Sockets 2 update or Windows 98 |
| rs_aix43 |
IBM RS/6000 with one or more 32- or 64-bit processors running AIX
4.3.3.10 or higher
|
| rs_aix51 |
IBM RS/6000 running AIX 5.1 with:
|
| sgi_65 | Silicon Graphics system with one or more processors running IRIX 6.5.x. Support is provided for the following CPU board types, as reported by the IRIX uname -m command: IP19, IP20, IP21, IP22, IP25, IP26, IP27, IP28, IP30, IP32, IP35 |
| sun4x_57 | Sun SPARCstation with one or more processors running the 32-bit or 64-bit version of Solaris 7 |
| sun4x_58 | Sun SPARCstation with one or more processors running the 32-bit or 64-bit version of Solaris 8 |
Beginning with this patch, the following will not be part of the AFS patch distribution. Although these system types will continue to be supported, we will provide e-fixes only on an as needed basis.
This section lists general information, requirements, and outstanding limitations and defects that apply to this patch release, categorized by system type. The notes are cumulative starting with Patch 1. The description of each note indicates when it was first noted.
In addition to the following notes, the product notes for all system types in the AFS Release Notes distributed with the GA release of AFS 3.6 also apply to this patch release.
Two butc binaries are now distributed with AFS 3.6. The default binary supports TSM 4.2. The additional binary (butc_4.1.2) supports TSM 4.1.2. The enabled binary is the one simply named butc. So, to provide support for TSM 4.1.2, move the butc that supports TSM 4.2 to a safe location or rename it (for example, butc_4.2), then rename butc_4.1.2 to butc. TSM 4.2 is supported on AIX 4.3, AIX 5.1 and Solaris 7, and 8. Multiple TSM Server support is enabled in the new butc.
(Noted at Patch 4)
The butc, backup, and buserver binaries must be at the same patch level on all machines that use the AFS backup utility.
(Noted at Patch 2)
On UNIX systems, AFS messages are now logged via syslog. Previously, AFS messages were logged to /dev/console. When /dev/console was unavailable, the process that was trying to write to it waited until it became available again; it was not possible to stop the process.
(Noted at Patch 1)
In addition to the following notes, the product notes for AIX in the AFS Release Notes distributed with the GA release of AFS 3.6 (build level afs3.6 2.0) also apply to this patch release.
The curpag binary is a small program that prints the pags for the current user session.
On AIX, when the user authenticates through kerberos, the KRBTKFILE environment variable is not set. If this environment variable is not set, the kerberos tokens are not displayed with the tokens.krb command.
The value of KRBTKFILE variable is of the following format: /tmp/tktp$PAG where $PAG are the pags associated with the current session. The curpag binary prints $PAG. To set the KRBTKFILE environment variable, issue the following command: $ setenv KRBTKFILE /tmp/tktp`/usr/vice/etc/curpag`.
The "curpag" binary is distributed with AFS on AIX 4.3 and 5.1 distributions and is in the /usr/vice/etc directory.
(Noted at Patch 4)
By default, garbage collection of tokens is disabled for AIX systems. To turn on garbage collection, run /usr/afsws/etc/gcpags, a toggle switch that enables and disables garbage collection. To verify whether garbage collection is enabled, run kdump -gcpags. If afs_gcpags=1 garbage collection is enabled; if afs_gcpags=2 garbage collection is disabled. For AIX 4.x systems, garbage collection works only if afs_gcpags_procsize has one of the following values: 256, 384, 416, 448.
For AIX 5.1, garbage collection will work irrespective of the value of afs_gcpags_procsize, which will always be 0.
(Noted at Patches 2 and 3)
In addition to the following notes, the product notes for AIX in the AFS Release Notes distributed with the GA release of AFS 3.6 (build level afs3.6 2.0) also apply to this patch release.
If AIX version 5.1 is installed, edit the /usr/lib/security/methods.cfg file instead of the /etc/security/login.cfg file as documented in IBM AFS Quick Beginnings.
The change affects Step 3 in the section titled Enabling AFS Login on AIX Systems in each of two chapters in IBM AFS Quick Beginnings: Installing the First AFS Machine and Installing Additional Client Machines. The corrected text follows.
Create or edit the DCE and AFS stanzas in the /usr/lib/security/methods.cfg file on the local disk:
Edit the stanzas as follows:
If you use the AFS Authentication Server (kaserver process):
DCE:
program = /usr/vice/etc/afs_dynamic_auth
options = authonly
If you use a Kerberos implementation of AFS authentication:
DCE:
program = /usr/vice/etc/afs_dynamic_kerbauth
options = authonly
If you use the AFS Authentication Server (kaserver process):
AFS:
program = /usr/vice/etc/afs_dynamic_auth
options = authonly
If you use a Kerberos implementation of AFS authentication:
AFS:
program = /usr/vice/etc/afs_dynamic_kerbauth
options = authonly
(Noted at Patch 3)
AIX 5.1 supports two types of local filesystems: JFS and JFS2.
(Noted at Patch 3)
Due to a change in the internal implementation of PAG based tokens in AIX 5.1, the command "id --G" can no longer be used to identify PAG based tokens. Therefore, the "tokens" command has been modified to additionally display the "type" of token being displayed, that is to say, PAG based token or UID based token.
For UID based tokens, the output of the tokens command looks like:
# tokens Tokens held by the Cache Manager (UID Based Tokens) : User's (AFS ID 1024) tokens for asf@jupiter.in.ibm.com [Expires Apr 11 10:43] --End of list--
For PAG based tokens, the output of the tokens command looks like:
# tokens Tokens held by the Cache Manager (PAG Based Tokens) : User's (AFS ID 1024) tokens for asf@jupiter.in.ibm.com [Expires Apr 11 10:43] --End of list--
(Noted at Patch 3)
At the time of this patch, TSM 4.1.2 is not supported on AIX 5.1, therefore, butc for AIX 5.1 does not support TSM.
(Noted at Patch 3)
In addition to the folowing note, the product notes for Digital UNIX systems in the AFS Release Notes distributed with the GA release of AFS 3.6 (build level afs3.6 2.0) also apply to this patch release.
AFS does not work with AdvFS, which is the default file system created on Compaq Tru64 v5.1 and 5.1a.
(Noted at Patch 4)
In addition to the folowing note, the product notes for HP-UX in the AFS Release Notes distributed with the GA release of AFS 3.6 (build level afs3.6 2.0) also apply to this patch release.
HP-UX 11i supports two types of local file systems: HFS and VxFS.
(Noted at Patch 4)
In addition to the following notes, the product notes for IRIX in the AFS Release Notes distributed with the GA release of AFS 3.6 also apply to this patch release.
Two new kernel extentions are provided to correct a condtion that prevented program execution in AFS space. These kernel modules can be used for IP20, IP22, and IP32 system types.
To install these modules, copy your existing libafs.IP20.a and libafs.IP20.o modules to a safe location, then rename libafs.IP20-R5000-1.0.a to libafs.IP20.a and libafs.IP20-R5000-1.0.o to libafs.IP20.o. Follow the same procedures to install the nonfs kernel modules.
For IP22 and IP32 systems, the new modules should be renamed as appropriate for the system, or links can point to the IP20 modules, for example libafs.IP32.a -> libafs.IP20.a.
(Noted at Patch 3)
As of the time of the Patch 1 release, the sgi_65 binaries are certified for all IRIX 6.5.x versions. This statement is true for all build levels of AFS 3.6, including the GA release.
(Noted at Patch 1)
The following note supersedes the first note in the section of the AFS Release Notes entitled Requirements and Limitations for Linux Systems. However, all other notes for Linux in the AFS Release Notes still apply to this patch.
(Linux 2.4 only) Due to a bug in the Linux kernels (2.4.2-2, 2.4.3-12), running kdump might cause the system to hang. A patch for this bug is available at: http://www.transarc.ibm.com/Downloads/afs36/index.html
This patch can be applied to the kernel as follows:
# cd /usr/src/linux-<kernel version> # patch -p1 < linux-2.4-dev-kmem-hang.patch
Rebuild and install the new kernel.
(Noted at Patches 3 and 4)
As of the time of the Patch 2 release, AFS 3.6 supports RedHat 2.4.x based Linux kernel versions. The AFS initialization script automatically selects the appropriate extensions file for the kernel version in use on the local machine.
(Noted at Patch 2)
As of the time of the Patch 1 release, AFS 3.6 supports all RedHat 2.2.x based Linux kernel versions. The AFS initialization script automatically selects the appropriate extensions file for the kernel version in use on the local machine.
(Noted at Patch 1)
In addition to the following notes, the product notes for Solaris in the AFS Release Notes distributed with the GA release of AFS 3.6 also apply to this patch release.
AFS 3.6 (build 2.6 and higher) supports the 32-bit or 64-bit version of Solaris 8.
(Noted at Patch 2)
Refer to the product notes for Solaris in the AFS Version 3.6 Release Notes. The note concerning installing SunSoft Patch 10654 for Solaris 7 also applies to this SunSoft patch.
(Noted at Patch 2)
As part of replacing the standard fsck program on an AFS File Server machine that runs Solaris, you make two changes in the /sbin/mountall script. The instructions for editing the /sbin/mountall script are in IBM AFS Quick Beginnings.
If you use Solaris 8 and apply SunSoft Patch 109576-01, the /sbin/mountall script is replaced and a new /usr/lib/fs/ufs/fsckall script is added. If you apply the patch on an existing File Server machine, the changes you already made in the /sbin/mountall script are overwritten.
case "$2" in
ufs) foptions="-o p"
;;
afs) foptions="-o p"
;;
s5) foptions="-y -t /var/tmp$$ -D"
;;
*) foptions="-y"
;;
cd /usr/lib/fs/afs ln -s /usr/lib/fs/ufs/fsckall
(Noted at Patch 2)
In addition to the following notes, all notes in the AFS for Windows Release Notes distributed with the General Availability release of AFS for Windows, version 3.6 also apply to this patch release.
In this patch, pthread.dll is renamed to afspthread.dll. Any scripts or application using AFS's pthread.dll must be modified to call the renamed library.
(Noted at Patch 4)
Backup on a file
Backup on a tape
The device path must be specified as \\.\tapedevice. For example, if the tape device is TAPE0, the dump path must be specified as \\.\TAPE0.
Common guidelines
Additional documentation notes
Due to file format differences between UNIX and Windows, the dump files are not cross compatible. Dump files created on a Windows machine can only be restored on a Windows machine.
(Noted at Patch 4)
A memory-mapped file is now used for the log, allowing it to be viewed after a system failure. In addition, the log can now be viewed remotely and descriptive text is displayed instead of error codes.
(Noted at Patch 1)
You can now install AFS for Windows components on a Windows 2000 machine. Windows 2000 Professional, Server, and Advanced Server editions are supported. Windows 2000 DataCenter Server edition and the use of TerminalServer services are not supported at this time.
There must be enough contiguous free disk space on the Windows 2000 machine to accommodate the size of the cache. For example, if you have 30 MB of free disk space on your machine and you intend to set a 20 MB cache, the cache configuration can possibly fail unless 20 MB of the available free space is contiguous.
(Noted at Patch 1)
A memory-mapped file is now used for the AFS Client trace log, allowing it to be viewed after a system failure. In addition, the log can now be viewed remotely and descriptive text is displayed instead of error codes.
(Noted at Patch 1)
You can now install AFS for Windows components on a Windows NT machine with Service Pack 6.
(Noted at Patch 1)
In order for an AFS Light user to access a cell, an entry for the cell must exist in both the AFS Light cell database (afsdcell.ini file) and the AFS Light Gateway cell database (afsdcell.ini file).
(Noted at Patch 1)
AFS Light must be able to resolve the name of the gateway machine in order to communicate with the gateway machine. The name of the gateway machine is the gateway's NetBIOS service name, in the form mach--afs, where mach is the host computer name up to a maximum of 11 characters. Name resolution can be achieved by adding the gateway's NetBIOS service name to the client's LMHOSTS file or to the appropriate DNS or WINS servers. If the AFS Light machine and its AFS Light Gateway machine reside on the same subnet, then name resolution succeeds automatically via a NetBIOS broadcast.
(Noted at Patch 1)
Once configured as an AFS Light Gateway, your AFS Client machine must be able to authenticate AFS Light users in a Windows context. This authentication can be achieved via a domain user account or via synchronized machine user accounts. A domain user account is a user account in a Windows domain. A machine user account is a user account that is valid only on a particular host machine.
When the AFS Light Gateway is configured into a Windows domain, an AFS Light user must log onto either a domain user account in the domain to which the gateway belongs or a machine user account with the same username and password as that of a domain user account in the gateway domain.
If machine user accounts are employed, then these accounts must be synchronized on the AFS Light Gateway and AFS Light machines. A user must log onto an AFS Light machine with the same username and password as that of a machine user account that is defined on the AFS Light Gateway machine.
The use of domain user accounts is recommended to simplify administration.
(Noted at Patch 1)
The AFS for Windows installation tool does not allow a user to install AFS components that have different version numbers. If you have more than one AFS for Windows component installed on your machine, you cannot update one component without updating all of the other components as well.
(Noted at Patch 1)
This section describes the defects fixed in each patch release, with the most recent release listed first. Defects are sorted by functionality within each patch release. Refer to the appropriate section:
This section describes the defects fixed in Patch 3. They are sorted into the following categories.
Server Defects Corrected in Patch 4
UNIX Client Defects Corrected in Patch 4
Windows Client Defects Corrected in Patch 4
(Solaris 7, 8) This fix resolves a machine deadlock caused by AFS not taking proper UFS locks prior to calling UFS functions.
(All) This fix resolves a fileserver deadlock (fileserver meltdown) that occurred when the fileserver experienced a very heavy load.
(Solaris 2.6, 7, 8) This fix resolves a machine deadlock during a reboot sequence caused by closing the socket descriptors in an incorrect sequence. This fix implements a sequence variable to ensure that the system closes a socket only after the process that was listening on the open socket has completed its operation.
(Windows) This fix resolves a condition where the AFS Client on a newly installed and configured AFS Server improperly displayed the status of volumes on /afs and /afs<cell name> as READ/WRITE. Previously, it was necessary to restart the AFS Client in order for the status to be properly displayed as READ-ONLY.
(Solaris) This fix merges the /etc/name_to_sysnum is file for several versions of Solaris. A check has been added in the afs.rc script for Solaris to check for valid values in the /etc/name_to_sysnum file. Incorrect values cause problems when AFS is starting.
(Windows) Previously, deleting a volume on a Windows AFS Server did not completely remove the .data directory. This fix resolves that problem.
(AIX) This fix resolves login and lsuser problems with the AFS authentication module caused by code changes in the security module of the AIX operating system.
(All) This fix resolves a condition where various volume related commands showed the used space of a volume as negative when the size of any file in the volume exceeded 2 GB.
(Windows) This fix resolves a condition on Windows AFS Servers where the klog command failed to authenticate for certain passwords.
(AIX 4.3) This fix resolves an infinite loop condition that caused fileservers to eventually meltdown.
(AIX 4.3) This fix adds a check to verify if the fields of the UUID structure have valid values. This identifier is used to manage clients with multiple IP interfaces.
(AIX) This fix corrects a problem where Kerberos tokens for logged in users were not visible on AIX systems.
(Digital UNIX 4.0) This fix resolves a condition on Digital UNIX 4.0 machines where an improper error message was displayed when removing a mountpoint. Previously, when the "fs rmm <mountpoint>" command was issued on an Digital UNIX 4.0 machine in AFS space, the mount was deleted, but an error message appeared stating "fs : file <mountpoint> does not exist."
(All) This fix prevents a condition that caused the NFS-AFS Translator (AFS Client) to panic when the NFS server forwarded requests from NFS clients to the NFS-AFS Translator before it was completely initialized.
(All) This fix resolves a vcache leak problem.
(Linux 2.2, 2.4) This fix resolves a race condition in the event handling code for Linux. This race condition results in processes losing wakeup calls; the process gets the wakeup before it actually goes to sleep. As a result, the process continues sleeping on events because it is waiting for a wakeup which has already occured, and it never returns from the system call. To the user, it appears as if the process has hung.
(Linux 2.4) This fix resolves a condition where a Linux client session hangs when a user issues the "su -" command from a terminal within a KDE environment.
This fix adds support for the -servers option in the klog command. The -servers option allows the user to specify the authentication server when retrieving tokens.
This fix resolves a condition where Windows AFS Clients did not correctly follow traversal rules.
This fix resolves a problem where, when the AFS Client GUI/Advanced tab page/checkbox "Start the AFS Client whenever the computer restarts" is checked, the following error message is displayed: Error Configuring Service-The AFS Client Service's startup parameters could not be changed. You might not have the authorization to perform this operation. Error 0x000003E5.
This fix resolves a condition where roaming profiles were not being created if the roaming profile path contained links.
This fix solves the problem of "?S" appearing in a volume label name on Windows 2000 machines when "dir" is issued from the Command Prompt.
This fix resolves a condition where, when the Windows AFS Client and Tivoli Policy Director Admin Client were both installed on the same machine, the afsd service did not start. This occurred because both programs used a pthread.dll file. The AFS file has been renamed to afspthread.dll.
This fix resolves a condition that prevented removing Global Drive Mappings in the Windows AFS Client.
This fix stops the AFS Client when the connection to the network is lost.
This fix writes a message to the event log whenever a Windows application requests a byte-range lock of a file in AFS space.
(All) This fix allows users to restore volumes with volume names in excess of 22 characters. It writes a warning into the ErrorLog/TapeLog file.
(All) This fix resolves the Dump Information problem with AFS backup for volumes larger than 2 GB.
(Windows) This fix suppresses the "License" dialog box during silent installs.
(All) This fix adds a -nodns flag to three vos commands: vos exa, vos listvldb, vol listvol. If -nodns is specified in the command line, the server names will be listed in IP format rather than as the host names.
(HP-UX 11.0) Undefined symbols for xdr_* were reported when using the AFS API on HP-UX. These missing symbols have been added to the librx.a file.
(Windows) This fix allows the Windows AFS Control Center Servers Manager to create volumes with unlimited quotas.
(Windows) This fix enables AFS backup to work on Windows systems.
(All) This fix adds a -showprogress flag to the butc command. If -showprogress is specified in the command line, progress will be displayed as dots when dumping or restoring a volume. Each dot represents 64 K of data.
This section describes the defects fixed in Patch 3. They are sorted into the following categories.
Server Defects Corrected in Patch 3
UNIX Client Defects Corrected in Patch 3
Windows Client Defects Corrected in Patch 3
This fix prevents the salvager fom deleting hardlinked files. By default, orphan files are ignored, but if the '--orphan remove' option is specified, orphan files are removed. The default of '-orphan' is ignore, which allows the salvager to comment about orphans on every run, but not to delete them.
This fix enables the kaserver process to authenticate krb-udp requests from Kerberos 4 clients.
While trying to get data from a ptserver, an error condition was not being checked. This caused a core dump of the fileserver. The function acl_CheckRights() now checks for an error condition.
A server panic was occurring as a result of a software assert (tweqi) caused by giving jfs_rele a vnode with a v_count=0. This resulted from insufficient locking. A VFS_LOCK for accessing the vnode list fom the VFS list was added to resolve this condition.
When a file on an NT fileserver was saved, the data was being corrupted. This did not occur when the file was created for the first time, but it occurred when an existing file was opened and saved after being edited. This defect corrects that problem.
(Linux only) Accessing AFS files through SAMBA caused refCount on inode to increase incorrectly and resulted in an "IPUT Bad refCount on inode" error. This fix resolves this problem.
This fix enables RX to properly track retransmitted packets.
(HPUX only) On HPUX 11.0, if the salvager were run on a partition that was greater than 4GB in size, it would delete the volumes in that partition. This fix solves that problem.
(IRIX only) This fix resolves a panic in afs_strategy.
(Linux 2.2only) This fix corrects a cache inconsistency problem with AFS under the Linux 2.2.* kernels.
(Linux only) This fix resolves a condition that caused the Linux OS to suspend processing because of a potential deadlock in memory handling routines.
(HP only) This fix allows the remsh command to function properly on HP11.
(Solaris 8 only) In Solaris 8, "df" was generating errors for AFS directories. This fix allows the df command to function properly in AFS directories under Solaris 8.
(HP only) This fix changes the startup script on HP 11. AFS used to panic when /usr/vice/cache was on VxFs. An afs.rc startup script corrects this problem.
With this fix, an AFS client queries the operating system on which it is installed during initialization. If the client is installed on the wrong OS, it will not start. This will prevent a Windows 98 AFS client from crashing a computer system that has been upgraded to Windows NT/2000.
Windows 2000 systems running AFS client would hang (100% CPU) when they were disconnected from the network.This fix resolves that condition.
This fix enables AFS clients on Windows 2000 running IIS to access a default page in AFS space.
This fix corrects a problem where AFS would not start over a PPP connection when a LAN adapter was present, but not active on the machine. This is a common scenario for laptops that connect via the LAN when in the office and via a modem when working remotely.
This fix provides a new binary that enables administrators to grant all users permission to start and stop an AFS service on a Windows NT/2000 system.
A default security descriptor on the afsd server permits the following access:
With this default, only Administrative users can start and stop the afsd_service. To allow all users to start and stop the afsd_service, the DACL of the AFS service object must be modified. The following command changes the DACL:
afsdacl [-set] [-revoke]
where:
-set sets the DACL on AFS service to allow all users
in USERS group to start and stop services.
-revoke revokes the DACL. Only administrators can start and stop services.
The afsdacl binary is installed in AFS/Client/Program.
Writing files into AFS space from a Windows 2000 client took longer than performing the same operation on a Windows NT client. This fix improves write performance on Windows 2000 clients.
If any icon in the system tray refreshes, Windows 95 considers this to be a screen refresh and restarts counting the amount of time that a system has been inactive.This can prevent a screen saver from starting. By default, the AFS tray icon refreshes every 3 minutes. This fix allows the user to set the refresh time of the lock icon by adding a registry entry.
Key: HKEY_LOCAL_MACHINES\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters Name: RefreshTimeInMinutes Type: DWORD Data: time in minutes
If not value is given for data, a default of 3 minutes will be used.
The menu that appears when right-clicking on the AFS tray icon was not disappearing unless the user opened and closed the AFS client window.This fix allows the user to dismiss the context menu by clicking elsewhere on the screen.
When tokens from NT clients were taken into a file and from this file were set into the cache manager of any UNIX system, the tokens command on the UNIX system was not printing correct values. This fix resolves this printing problem.
In AFS Windows clients, wildcard matching was not done correctly during a search, for example, if, from the command prompt, "dir /s *.txt" was submitted, files with the .txt extension were not shown in the results. This fix adds support for wildcard matching on Windows 2000/NT systems.
This fix enables kdump to work properly on 64-bit Solaris.
This fix enables special characters, such as colons, to be included in a field in the bulk file used by the uss_bulk command by escaping them with a backslash. The ':' is traditionally used to separate fields. In order to include it within a field, you must escape the ':' using the '\' (backslash). A ':' in a field is represented by '\:'. The '\' character itself can be represented by '\\'.
The fix allows the bos server to perform its function correctly, along with the option setrestart -server <machine name> -time "now".
Before this fix, when the command was issued to restart the bos server at any instant by specifying the option "now", the bos server was restarting every minute. This was shown in the log file /usr/afs/logs/BosLog. This fix resolves that problem by updating the proper values in the BosConfig file.
When an AFS client was installed for the Japanese language, the AFS menu, which is shown when you right-click on any AFS folder in Windows Explorer, was not showing up. This fix corrects that error.
AFS command line syntax allows argument switches to be omitted if the arugments are in order. This fix solves a defect that caused the "pts" command to fail if the arguments were not accompanied by switches.
This section describes the defects fixed in Patch 2. They are sorted into the following categories.
This fix enables the remove mountpoint command (fs rmm) to follow symbolic links. Previously, if a symbolic link was encountered, the mount point was not removed.
This fix resolves a problem that occurred when an AFS File Server received requests from AFS Client machines to which it could not respond. The requests locked up threads in the File Server and rendered the server unusable.
This fix prevents the File Server from generating a core file when calling the following functions in the TAdd code module: AddCallBack1_r and MultiBreakCallBack_r.
This fix modifies the behavior of the backup dump process by preventing the creation of dumplevels with spaces in the name.
This fix modifies the behavior of the BOS Server (bosserver) to automatically restart only when the timestamp changes on a binary. Previously, the BOS Server restarted processes when permissions were changed on binaries, even if there was no change to the timestamp of the binaries. This happened because the st_ctime time field was used to determine when to restart processes. Now, st_ctime is replaced by st_mtime as the reference time field. Therefore, processes are restarted only when the binary itself changes.
This fix enables the kaserver process to authenticate krb-udp requests from Kerberos 4 clients.
This fix improves File Server responses for Windows clients. It was previously possible for users (mostly those using Windows NT Explorer) to experience a delay before a "Permission denied" error was returned when accessing directories with the following access permissions: system anyuser li. Users can now run the File Server with the -dontdelay switch to prompt the File Server to more quickly return the "Permission denied" error.
This fix prevents an infinite loop situation from occurring when the timeout chain receives a faulty link. Now, when a faulty link is encountered, a message if added to the log file.
This fix resolves a condition that caused the AFS client to panic when server structures are no longer valid.
(Linux only) This fix resolves a condition that caused Linux systems to suspend processing (hang) during a shutdown or reboot.
This fix resolves a condition that caused the 'vos backupsys' command to fail when run by the bosserver as a cron job. On Linux, when the bosserver runs a process that tries to write to stdout/stderr, the process receives a SIGPIPE and fails. Although this error appeared only on Linux, code changes were made on all platforms to prevent processes that are started by the bosserver from writing to stdout/stderr.
This fix enables AFS to return an ENODEV (error, no device) response when an invalid mount point (device) is encountered. Invalid mount points occur as a result of unknown cells or volumes.
(Solaris only) This fix resolves a condition where a list command (ls) returned an error of "Value too large for defined data type" when it encountered an AFS file with a negative date.
This fix eliminates a buffer overflow that had been occurring in VIOCSETVOSTAT pioclt.
This fix resolves a race condition in the fileserver wherein the fileserver attempted to use a mutex that was not initialized.
(Linux only) This fix enables the use of double cellname entries within the CellServDB file. In such an entry, the second cell name is used for AFS/DFS translator purposes.
(Solaris only) This fix resolves package segment faults that occurred when the package client attempted to update files with long pathnames. The buffer provided to the file that is used to hold diagnostic messages, messages.c, overflows when the package program attempts to modify files with long pathnames. This was resulting in package segmentation faults. The buffer has been increased from 128 bytes to 256 bytes.
(Linux only) This fix closes potential security holes.
(Solaris 8 only) This fix resolves a condition that caused an AFS Client on a SparcStation 20 to panic while accessing AFS files.
(Solaris only) This fix resolves a condition that caused an AFS client to suspend processing (hang) when configured with a memory cache greater than 2 GB.
(Linux only) This fix improves performance on Linux clients.
(HP only) This fix resolves a condition that caused the HP CDE screen to hang.
This fix enables usernames to contain a period, for example, username.admin.
This fix resolves a condition that caused setup files to fail to execute if the were deeply nested within an AFS directory.
This fix improves token management.
For kerberos authentication, two new binaries have been created: C:\Program Files\IBM\AFS\Client\Program\klog_krb.exe and C:\Program Files\IBM\AFS\Common\afsauthent_krb.dll. To use kerberos authentication, rename these binaries to klog.exe and afsauthent.dll.
This fix resolves a condition that caused a GUI account manager being used to unlock an account to fail with an error message of "No servers appear to be up".
This fix improves the readability of the log file by removing excess blank lines.
This fix removes an existing cache file during start up.
This fix resolves a condition that caused the AFS NT client to crash in smb.c.
This fix resolves a condition on Windows 2000 clients that prevented the AFS client from removing temporary files.
This fix resolves a condition that caused the login screen to display an error dialog box stating that a problem existed in services.exe and that the workstation would automatically restart in 60 seconds. Microsoft also addressed this problem using a hotifx (see http://support.microsoft.com/support/kb/articles/q266/0/66.asp).
This fix enables silent installs on Windows 2000.
This fix prevent MS Visual C++ v6.0 from altering the timestamp whenever a file is opened and closed without being altered.
This section describes the defects fixed in Patch 1. They are sorted into the following categories.
Server Defects Corrected in Patch 1
UNIX Client Defects Corrected in Patch 1
Windows Client Defects Corrected in Patch 1
Windows Control Center Defects Corrected in Patch 1
This fix changes the AFS server processes to log messages via syslog. Previously, AFS wrote to /dev/console. When /dev/console was unavailable, the process that was trying to write to it waited until it became available again; it was not possible to kill the process.
This fix eliminates one potential cause of timeouts when the vos listvol command has to produce output about a large number of volumes. As it processes this command, the Volume Server no longer writes to disk the three index files (large vnode, small vnode, and header) associated with a volume.
(Linux 2.2 only) When restarting the bosserver process using the bos restart command, the process stopped but did not restart. Now, when the bos restart command is issued for the bosserver process, the process is correctly restarted.
This fix enables the File Server to shut down properly if it receives the signal to shut down while attaching volumes.
Previously, it was difficult to use a firewall with a network address translator (NAT). This enhancement enables users to have a File Server register inactive (or fake) IP addresses in the Volume Location database, thus allowing client machines outside the NAT to be able to access File Servers. In order to add fake IP addresses for server processes, add f as the first character in the NetInfo line for the corresponding IP address. For example, add:
f 10.10.3.100
This IP address is registered for the server process, but it is registered without being checked for a physical connection.
(Solaris only) This fix eliminates a race condition in the File Server's h_ReleaseClient_r routine and so prevents the File Server from generating a core file.
(Solaris only) This fix prevents the File Server from generating a core file, which occurred when a NULL value was passed to the rx_NewCall function.
This fix prevents the File Server from failing when a file is being simultaneously accessed (created or read) and deleted.
This performance enhancement limits the number of Volume Location Database entries that are searched by the Volume Location Server to 2000. Previously, it was possible for requests to become backed up on the Volume Location Server when the server was searching the entire Volume Location Database for a few entries.
(Windows only) When using the Server Configuration Wizard, replicating root volumes failed if replicas already existed elsewhere. No error message was displayed when this occurred. This problem has been corrected and root volumes can now be replicated using the Server Configuration Wizard.
This fix prevents remote procedure calls (RPCs) requesting impermissible operations to read-only volumes (such as rename, link, remove) from being made to File Servers; however, it allows sending RPCs to File Servers for file open operations when the file already exists.
(AIX 4.3 only) When reading volume information, the number of bytes read did not always equal the actual size of the structure. This caused AFS to fail. The VolumeItems file is now read multiple times before AFS fails in order to increase the chance of a successful read.
This fix also corrects a client hang problem that appeared after the machine attempted to access a directory that contained a significant number of mount points.
(AIX 4.3.2 only) This fix eliminates a problem that resulted from writing a large number of bytes to an invalid address in AFS. Previously, it was possible that when writing a large number of bytes to an invalid address in AFS, the file could become full, resulting in an infinite loop in the kernel, and the process could not be stopped.
The pts createuser command did not function properly when used with positional parameters. This problem has been fixed and users can now specify the parameters explicitly or identify them by following the rules of positional parameters.
(Solaris only) This fix corrects a problem that occurred when a process attempted to access the proc file system.
(HP-UX only) This fix prevents a problem that resulted in AFS client machines not responding.
(Linux only) This fix corrects a cache inconsistency.
When using the Windows Command Prompt to rename a file in the AFS filespace to be identical to an already existing file in the same AFS location, the already existing file was overwritten. This was not the desired behavior. Now, in this situation, the user is warned of the existence of a file with the same name and the file is not automatically overwritten.
The error dialog box that was displayed when users attempted to obtain AFS tokens on a machine that had an incorrect date setting was misleading and partially unreadable. Now, the error message displayed is readable and contains more information.
Previously, users were unable to map network drives using the graphical user interface when the root directory was not /afs. Now, when using a root volume other than /afs, users can map network drives using the graphical user interface.
When using AFS Light and writing to the AFS filespace (saving, copying, etc.), seven hours were added to the time stamp associated with the file. This problem has been fixed and the time associated with files in the AFS filespace is now correct.
This enhancement improves the AFS Client's trace logging. A memory-mapped file is now used for the log, allowing it to be viewed after a system failure. In addition, the log can now be viewed remotely and descriptive text is displayed instead of error codes.
This enhancement enables the AFS Client to support all LAN Adapter (LANA) numbers. The client now automatically detects and uses all available LANA numbers.
The Lan Adapter Number field on the AFS Client's Miscellaneous Configuration Dialog Box is now disabled. As of the Patch 1 release, the AFS Client automatically detects and uses all available LAN Adapter (LANA) numbers. Use of the Lan Adapter Number field could possibly result in users unknowingly disabling the auto-LANA functionality. If necessary, you can fix the LANA number used by the AFS Client service to a specific value by using the LANadapter Registry key, which is found under the following Registry setting:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters
Previously, non-relative symbolic links to the AFS root did not function correctly. The problem has been identified and corrected.
When restarting a process using the graphical user interface in the AFS Server Manager, all server processes were restarted. This problem has been fixed.
(Solaris only) This fix enables remsh commands that point to an AFS version of rsh to be issued to remote machines and to work as expected, producing the same results as issuing remsh commands that point to native rsh.
This enhancement improves the startup time to start dump by allowing temporary volume sets to be created local to the backup process and not stored in the Backup database. This reduces activity on the Backup Server.
(Linux only) This fix enables AFS to shut down cleanly.
Previously, it was possible to easily create volumes with names that exceeded the character limit. With this fix, a warning is now displayed when users create volumes using volume names with more than 22 characters. Also, the backup system displays a warning when backing up a volume will result in a new name containing more than 22 characters.
This fix adds an additional step to the CheckVLserver routine to determine the definitive status of the servers. Previously, it was possible for AFS client machines to be unable to access volumes in foreign cells even though the Volume Location Servers (vlservers) in those cells were available. This was due to the CheckVLserver routine accessing conflicting variable settings.
(Solaris 2.6 only) This fix eliminates kernel panics that sometimes occurred.
(Linux only) This fix eliminates a kernel memory corruption that sometimes occurred.
This fix resolves an RX error that resulted when operating systems were mixed in the AFS environment. The operating system combinations that caused the error were AIX with Linux and Windows NT with Solaris.
This fix resolves an error that occurred when a CERT advisory was issued due to a buffer overflow in Kerberos 4 and Kerberos 5.
This fix prevents the butc process from failing while talking to an ADSM server by avoiding contention for a pthread lock.
This enhancement provides a new version of the SGI kernel to work with the SGI IP35 chip.
(Solaris only) This fix prevents a panic in osi_NetReceive on Solaris machines.
(Linux only) This enhancement provides changes to the AFS initialization script. The initialization script automatically selects the appropriate extensions file for the kernel version in use on the local machine. The module for the kernel that is closest to the installed kernel version is now chosen; whereas previously, the script only chose modules compiled specifically for the installed version.
(AIX 4.3 only) This fix resolves a programming error that resulted in a client deadlock.
(AIX 4.3.3 only) With this enhancement, an error message is now displayed if the klog command is used with the -setpag option when the user is logged on as root.