NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: This Patch Fixes Problems in the NFSSERV.NLM DOCUMENT ID: TID000214 DOCUMENT REVISION: B DATE: 25MAR94 ALERT STATUS: Yellow INFORMATION TYPE: Symptom Solution README FOR: NFS113.EXE NOVELL PRODUCT and VERSION: NetWare NFS 1.2 ABSTRACT: This NetWare NFS 1.2, Patch 6, contains improvements and fixes for NFSSERV.NLM, LOCKD.NLM, NFSADMIN.NLM and NFS.NAM in NetWare NFS Release 1.2. NFS113.EXE contains the following fixes: 1) Time reduction in file creation time in large subdir (4000+files) 2) Time reduction in adding NFS name space to large volumes (500 MB) 3) Mount time reduction for large volumes 4) Transfer time enhancement (5) New option in setting AGING_INTERVAL 6) Fixes permissions problems with share violations 7) Lock enhancement for NFS 1.2, revision A. ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ SYMPTOM When trying to access files by multiple clients where the files are just closed by one client, occasionally the following message is displayed: MESSAGE Sharing Violation SYMPTOM The parent directory's write permission is removed when creating a subdirectory with an access mode of 0775 and umask of 022. SYMPTOM Sometimes (rarely), during the execution of the nfsstop.ncf script, the following server abend message is return: MESSAGE ReturnNonMovableMemory called with invalid return segment... SYMPTOM The use of Unix cpio utility to restore a large directory that has many read-only files will generate write errors with some files not being restored correctly. SYMPTOM The "write error" from the file save operation of certain multiple-platform applications. SYMPTOM Time for file loads from volumes mounted by PC-NFS with /MS (must share) option is lengthy. SOLUTION Apply the files found in NFS113.EXE file. Self-Extracting File Name: NFS113.EXE Revision: B Files Included Size Date Time \ NFS113.TXT (This File) PATCH.EXE 76981 01-30-92 5:00a NFS113.RTP 38460 05-14-92 6:22p Installation Instructions: REQUIREMENTS This procedure will require the NetWare server to be brought down to update the NetWare NFS Name Space. The procedure for applying the update to the NLMs for NetWare NFS 1.2 will be to transfer the files from the distribution diskette, apply the patch, then transfer the patched files to the NetWare server. The NetWare NFS Name Space file, NFS.NAM, will be transferred to a floppy diskette, then copied to the server. This procedure requires a workstation with a floppy diskette drive the same format as the distribution diskette. The workstation should be connected to the server and the user will log in to the server as SUPERVISOR. The files to be patched have the following module descriptions: - NetWare 386 NFS V1.2 (911122) - NetWare 386 NFS Lock Manager V1.2 (911122) - NetWare 386 NFS Name Space Support V1.2 (911122) - NetWare NFS Administration Utility V1.2 (911122) After the patch is applied, the module descriptions will be the following: - NetWare 386 NFS V1.2 (920512) - NetWare 386 NFS Lock Manager V1.2 (920306) - NetWare 386 NFS Name Space Support V1.2 (920306) - NetWare NFS Administration Utility V1.2 (920512) UPDATE PROCEDURE I. Preparation Before starting the PATCH procedure, make sure you have the following items: þ NetWare NFS 1.2 distribution diskette. þ A workstation with a floppy disk drive of the same format as the distribution diskette. þ Patch Files on hard disk or floppy diskette. This procedure will assume the files are on a floppy diskette. þ A blank floppy diskette to transfer the NetWare NFS Name Space file. For this procedure: Drive C: is assumed for all activities on the workstation. Drive A: is assumed for all activities related to the floppy disk drive. Drive F: is assumed for all activities related to the NetWare server. A temporary directory is created for this procedure using the name TEMP. If this name is already used on the workstation, use another name for the temporary directory where TEMP is specified in this procedure. II. Updating the NLMs 1. Create a temporary directory on the workstation. This directory will contain the PATCH files and the NLMs. (This procedure assumes the temporary directory is created on the C: drive. Substitute the actual drive letter to be used for C: drive.) C: MKDIR \TEMP 2. Transfer PATCH files, NFS113.RTP and PATCH.EXE, to the TEMP directory. (This procedure assumes the files are on a floppy diskette. Substitute the actual location of the files for A: drive.) CD \TEMP COPY A:*.* 3. Place the NetWare NFS 1.2 distribution diskette in the A: drive and transfer the NLMs from the distribution diskette to the directory TEMP. Drive A: is assumed. COPY A:\SYSTEM\NFSSERV.NLM COPY A:\SYSTEM\LOCKD.NLM COPY A:\SYSTEM\NFSADMIN.NLM COPY A:\NFS.NAM 4. Execute the PATCH file with the name of the .RTP file as the argument. PATCH NFS113 Note: PATCH.EXE searches for file names starting from the current directory then searches paths specified in the DOS PATH environment variable. If there are files with the same names as those being patched in other directories specified in the DOS PATH, a message "New version already exists" is displayed. III. Transferring the NLMs to the Server 1. Log in to the file server as SUPERVISOR. LOGIN fileserver/SUPERVISOR Password:XXXXXX 2. Save a backup copy of the current files to be updated. F: CD \SYSTEM NCOPY NFSSERV.NLM NFSSERV.OLD NCOPY LOCKD.NLM LOCKD.OLD NCOPY NFSADMIN.NAM NFSADMIN.OLD NCOPY NFS.NAM NFS.OLD 3. Use FLAG to remove the READ-ONLY attribute. FLAG NFSSERV.NLM N FLAG LOCKD.NLM N FLAG NFSADMIN.NLM N FLAG NFS.NAM N 4. Copy the updated files to the SYSTEM directory. NCOPY C:\TEMP\NFSSERV.NLM F:\SYSTEM\NFSSERV.NLM NCOPY C:\TEMP\LOCKD.NLM F:\SYSTEM\LOCKD.NLM NCOPY C:\TEMP\NFSADMIN.NLM F:\SYSTEM\NFSADMIN.NLM NCOPY C:\TEMP\NFS.NAM F:\SYSTEM\NFS.NAM 5. Use FLAG to reset the READ-ONLY attribute. FLAG NFSSERV.NLM RO S FLAG LOCKD.NLM RO S FLAG NFSADMIN.NLM RO S FLAG NFS.NAM.NLM RO S 6. The patched NFS.NAM (920306) *MUST BE* installed in the file server's NetWare boot directory in the same DOS partition where SERVER.EXE resides. Transfer the name space module to a floppy diskette using the following command: NCOPY NFS.NAM A: IV. Loading the New Files. Operations for this phase of the update will be performed from the NetWare server. 1. At the NetWare console, shut down the server. This is necessary to update the NFS Name Space. :NFSSTOP :DOWN :EXIT 2. At the DOS prompt, copy NFS.NAM to create a backup file. COPY NFS.NAM NFS.OLD 3. Transfer the name space module from the floppy diskette to the NetWare boot directory on the file server's local DOS partition. C:\NETWARE is assumed. COPY A:NFS.NAM C:\NETWARE\NFS.NAM 4. Restart the server. SERVER NFS should be working with the updated files. Please check the new versions by running the following command: MODULES V. Post Patch Clean Up 1. At the workstation, delete the existing files in the TEMP directory. C: CD \TEMP DEL *.* 2. Remove the TEMP directory. CD \ RMDIR \TEMP The update is now complete. Patch History: This patch supersedes the previous patch for these modules. PTF-F111 (NFS111.EXE) Solution Specifics: 1. Time to create a file in a directory of more than 4000 files is now under one minute. 2. Time to add NFS name space to large volumes (greater than 500 MB) with many files is reduced. 3. Mount time for huge volumes has been reduced. The mount time for a 800 MB volume is about three minutes. 4. Time to transfer files greater than 10 MB is reduced. 5. AGING_INTERVAL 0 is supported for cross platform applications where there is a need to close a file immediately after reading and writing the file to make the file available for another read/write operation. Note: Setting the AGING_INTERVAL to 0 will impact the performance of NetWare NFS and should only be done if the application requires immediate closure of files after a read/write operation. ÿ