Release Notes Product: FileServ® for UNIX® Version 4.4.1 Operating Systems: IRIX® 6.5.6M, 6.5.7M, 6.5.8M, 6.5.9M and 6.5.10M SPARC™ Solaris™ 7 and 8 Date: October 8, 2001 NOTE: (1) The operating system must always be run in US_English. (2) FileServ supports the maintenance (M) version of IRIX 6.5.x, as opposed to the feature (F) version. (3) To obtain details on supported application server platforms, contact your FileServ sales representative.
Purpose of This Release This release contains corrections to problems encountered in previous versions. Fixed Problems The following table lists fixed problems: Operating System Problem Number All 564 When the db map is created in fsaudit, all directories in dirdb are added. The update_mask field in the db map entry indicates whether or not the directory should be there. This field was not being initialized, so directories were occasionally being reported as missing even though they existed.
Documentation In addition to the FileServ software, the distribution CD contains the FileServ technical documentation as PDF files as well as an Adobe® Acrobat® Reader. The Reader allows you to view and navigate the electronic book files yet preserves the page design and graphics from the printed books. Order Printed Books To order additional printed books, complete this form and send it to your ADIC Sales Representative: Version 4.4 Book Quantity Version 4.
Drive Type Quantum DLT 4000 Supported on IRIX Supported on Solaris Yes Yes Yes Yes Yes Yes Yes Yes Quantum DLT 7000. Configure this drive as a DLT 4000. Quantum DLT 8000. Configure this drive as a DLT 4000. Sony AIT-1 SDX-300 Sony AIT-2 SDX-500 Sony GY-10 Sony GY-2120 Sony GY-8240.See “Modify IRIX Kernel for SONY DTF-2 Drive” on page 5 of these"Release Notes." During initial configuration on VolServ, set these drives up to support both DTF1 and DTF2 media types.
If you are adding an AIT-2 drive, update the DEF_MED_SPC_AIT parameter definition to be as shown below if you are using 230m tape: DEF_MED_SPC_AIT=50000000000; If you are adding an 3590E1A drive, update the DEF_MED_SPC_3590 parameter definition to be as shown below: DEF_MED_SPC_3590=20000000000; If you are adding a DLT 7000 drive, update the DEF_MED_SPC_CTIV parameter definition to be as shown below: DEF_MED_SPC_CTIV=35000000000; If you are adding a DLT 8000 drive, update the DEF_MED_SPC_CTIV parameter d
Step 4. Rebuild the kernel. # autoconfig -f Step 5. Reboot the machine. Compatibility with VolServ® FileServ VolServ Version 4.4.1 Version 5.0 Version 4.4 Version 4.1 NOTE: The release numbering scheme has been changed on VolServ to correlate with the release numbers on FileServ. Version 4.3 Version 4.2 Version 4.1 Version 4.0 Version 3.0 Version 2.3.3 Version 3.5.2 Version 2.3.3 Version 3.5.1 Version 2.3.2 Version 3.5.0 Version 2.3.1 Version 3.4.3 Version 2.3.3 Version 2.3.2 Version 2.3.
Operating System Requirements Patches NOTE: ADIC recommends that you install all required Y2K patches for your machine. Make sure you install all the patches that your vendor recommends for your kernel, operating system, network, hardware, media, drive type, and storage devices. Additionally, ADIC requires the patches, filesets, or packages listed below to successfully operate FileServ. Obtain these patches from the appropriate vendor. Platform Patch Description IRIX 6.5.
fspolicy COMMAND • Running the fspolicy -w command on a large (greater than 500,000 entries) file system can take several hours to complete. If the fspolicy command is unable to store or truncate files, or if the fspolicy command is killed or terminates abnormally, run fspolicy -w to rebuild the candidate files. GUI PERFORMANCE (CR #296) • Before running another command in the GUI, select the button and the remove the Status Window. Performance problems may occur if this is not done.
where: Option device_name Description Path to the storage device. For example, /dev/rmt/tps0d6nrv. Step 4. Save the changes and quit the edit session. Step 5. Stop the mediad process. # mediad -k Step 6. Re-start the mediad process. # mediad Upgrading from FileServ Version 3.4.2 and Later The Vista Database locking type was modified to use the IP locking mechanism. Therefore, to reinitialize the transaction activity file, follow the steps below: Step 1. Stop FileServ. Step 2. Run checkpoint.
Step 5. Change directory to $FS_HOME/internal/fsdb and move each file with a .dbd extension to the same name .dbd.old. There should be one fs1_#.dbd and fs5_#.dbd file for each file system managed by FileServ. cd $FS_HOME/internal/fsdb mv fileserv2.dbd fileserv2.dbd.old mv fileserv3.dbd fileserv3.dbd.old mv fileserv4.dbd fileserv4.dbd.old mv fs1_4.dbd fs1_4.dbd.old mv fs5_4.dbd fs5_4.dbd.old ... Step 6. Change directory to DDL and modify the fs3.
to: char drdmhdl[64][1]; Step 11. /* DMIG handle binary data */ Get the numbers for both the fileserv5 and fileserv1 databases to be regenerated by using ls For example, if fs1_4.dbd.old and fs5_4.dbd.old are returned the number is 4. There should be one pair of these files for each file system associated with FileServ. If the fs5_#.dbd.old file does not exist, make a note and do NOT run the ddlp for the fs5.ddl in Step 11 for this number (the fs1_4.dbd should still be run). fs1_*.dbd.old. Step 12.
Contents of Version 4.4 OPERATING SYSTEMS • IRIX® 6.5.6M, 6.5.7M, 6.5.8M, 6.5.9M and 6.5.10M • SPARC™ Solaris™ 7 and 8 FIXED PROBLEMS The following table lists fixed problems: Operating System Problem Number All 539 The fsmedcopy command fails for some clustered tapes. All 541 Cannot send a recover command to DTF drives with fs_scsi. All 543 Return codes need to be MRS codes. All 544 Overwrite occurs if clustering is enabled and unexpected EOT is hit.
Contents of Version 4.3 OPERATING SYSTEMS • IRIX® 6.2, 6.5.4M, 6.5.5M, 6.5.6M, and 6.5.10M • SPARC™ Solaris™ 2.6, 7, and 8 NEW DRIVE SUPPORT • Additional drives supported by this release of FileServ include the following: - IBM 3580 LTO - Solaris only until supported by IRIX tpsc device driver MAXIMUM NUMBER OF TAPE COPIES RAISED(#493) • The maximum number of tape copies for a file has been raised to four.
Operating System Problem Number All 499 Policy will trashcan file if db valid tape != disk All 500 Checkpoint tar command needs to follow links All 503 Mapping has /fs link hardcoded instead of using $FS_HOME All 504 fs_dump fails if mount point not at root All 505 fsckp script doesn’t handle /mnt/vol05 mntpt All 506 fspolicy not initializing hash lists All 508 Change fs_bld_maplist to space out fs_map_dir All 509 Add logfile to newfslog script All 510 mda2 perf point causes fs_s
Previous FileServ Releases For information about previous features and fixes to the base software code, refer to prior “Release Notes.” These Notes: • Can be found on the secured site. See “Related Publications” on page 3 of these"Release Notes." • Or, contact your FileServ sales representative.
Copyright 2000, 2001 by ADIC, Advanced Digital Information Corporation. All rights reserved. ADIC, AMASS, CentraVision, DataMgr, EMASS, FileServ, and VolServ are either trademarks or registered trademarks of ADIC. All other brand or product names are trademarks or registered trademarks of their respective companies. Direct comments to: ADIC, 10949 East Peakview Avenue, Englewood, CO 80111 USA, Phone: 303-792-9700, FAX: 303-792-2465. www.adic.com, Software publications: techdocs@adic.
