ملخص المحتوى في الصفحة رقم 1
Release Notes
®
Product: FileServ™ for UNIX Version 4.3
®
Operating Systems: IRIX 6.5.6M, 6.5.7M, 6.5.8M, 6.5.9M and 6.5.10M
SPARC™ Solaris™ 7and 8
Date: February 2, 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.
Contents
Page Topic Page Topic
1 Prerequisites 7 Mo
ملخص المحتوى في الصفحة رقم 2
Purpose of This Release This release contains enhancements and corrections to problems encountered in previous versions. A summary of major items follows: NEW DRIVE SUPPORT (#527) • Additional drives supported by this release of FileServ: - IBM 3580 LTO - Solaris only until supported by IRIX tpsc device driver NEW OS SUPPORT (#507) Add support for Solaris 8 - Requires Veritas VxFs version 3.3.3 + patch01 Add support for IRIX 6.5.10m MAXIMUM NUMBER OF TAPE COPIES RAISED(#493) The maximum nu
ملخص المحتوى في الصفحة رقم 3
Operating Problem Description of Problems Fixed in Version 4.3 System Number All 495 Crtl-C during a fsretrieve while mo is flipping causes crash All 496 DTF/DTF2 fs_sysparm Comment Wrong All 497 fs_copyman not intializing move requests properly All 498 Memory overwrite in scsi code when using scsi pass through device 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
ملخص المحتوى في الصفحة رقم 4
The following table lists unresolved problems: Operating Problem Description of Known Problems in Version 4.3 System Number IRIX 588 When fsundelete command is executed, occasionally it does not completely 936 undelete all the files on the undelete list because of a timing issue. Solaris 958 Workaround: To overcome this problem, run the fsundelete command again on the unrestored file(s). Thefsundelete command does not retrieve any secondary copies of files that were deleted, only the primary cop
ملخص المحتوى في الصفحة رقم 5
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.1 Book Quantity Version 4.1 Book Quantity FileServ Overview, #60
ملخص المحتوى في الصفحة رقم 6
Supported Drives FileServ supports the following drives on the specified platforms: Supported Supported Drive Type on IRIX on Solaris Ampex DST 310. Yes No Ampex DST 312. See NOTE below. Fujitsu M8100. Configure this drive as an IBM 3590B1A. Yes Yes HP 2600FX MO. Yes No HP 5200EX MO. IBM 3590B1A. Yes Yes IBM 3590E1A. Do not configure these drives on an RS-422 port. IBM 3580 LTO No Yes Quantum DLT 4000. Yes Yes Quantum DLT 7000. Configure this drive as a DLT 4000. Quantum DLT 8000. Configure this
ملخص المحتوى في الصفحة رقم 7
Update sysparm File with Media Capacity After an initial installation, if you add or change a Sony AIT-2, IBM 3590E1A, Quantum DLT 7000, or Quantum DLT 8000 drive type, update the system parameters to reflect the new media capacity by following the steps below: Step 1. Log in as root. Step 2. Edit the fs_sysparms file. # vi /$FS_HOME/sysparms/fs_sysparms Step 3. 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 170m tape: DEF_
ملخص المحتوى في الصفحة رقم 8
Step 2. Search the scsi file and look for the words “GY-8240.” # vi /var/sysgen/master.d/scsi Step 3. If that text is not found, add the following entry to the file for your drive: /* SONY GY-8240 drive */ { SONYGY, TPGY2120, 4, 7, "SONY", "GY-8240", 0, 0, {0, 0, 0, 0}, MTCAN_BSF|MTCAN_BSR|MTCANT_RET|MTCAN_CHKRDY|MTCAN_PREV| MTCAN_SEEK|MTCAN_APPEND|MTCAN_SILI|MTCAN_VAR|MTCAN_SETSZ| MTCAN_CHTYPEANY | MTCAN_COMPRESS, 20, 100*60, 10*60, 9*60, 9*60, 16384, 256*1024, tpsc_default_dens_count, tpsc_def
ملخص المحتوى في الصفحة رقم 9
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.8f SG0004026 Fixes lost
ملخص المحتوى في الصفحة رقم 10
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, runfspolicy -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. Pa
ملخص المحتوى في الصفحة رقم 11
Installation and Upgrade Issues If you are installing FileServ or upgrading an existing FileServ installation, review the following topics to make sure FileServ is correctly installed. For complete and detailed installation instructions, refer to the Installing FileServ book. Topic Page Turn off mediad on SGI Platforms 11 Upgrading from FileServ Version 3.4.2 and Later 12 Upgrading from FileServ Earlier than Version 3.4.2 12 Installing FileServ and AMASS on the Same Platform 15 Turn offmediad on
ملخص المحتوى في الصفحة رقم 12
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 3. Install the latest versions of FileServ. Step 4. Run $FS_HOME/util/buildtaf -i. Step 5. Execute “D” option. Step 6. Quit the program. Step 7. Restart FileServ. Upgrading from FileServ Earlier than Version 3.4.2 Changing to the new Vista
ملخص المحتوى في الصفحة رقم 13
Step 8. Run the following commands shown below: ddlp fs2.ddl ddlp fs3.ddl ddlp fs4.ddl Step 9. Remove fileserv*.h; move fileserv*.dbd, and change directory: rm fileserv*.h mv fileserv*.dbd .. cd .. Step 10. Modify the "fs1.ddl" file as follows: a) Find the "record fileattr_rec {" line b) Modify the following line from: char fadmhdl[64]; /* DMIG handle binary data */ to: char fadmhdl[64][1]; /* DMIG handle binary data */ c) Find the "record dirdb_rec {" line d) Modify the following line from: cha
ملخص المحتوى في الصفحة رقم 14
Continue modifying all _5 names to_4 (there should be 17 of them forfs1.ddl file and 14 in the fs5.ddl file). Step 13. Run both ddlp fs1.ddl and ddlp fs5.ddl commands to generatefs1_#.dbd and fs1_#.dbd files. Be sure to skip the fs5_#.dbd files if the corresponding fs5_#.dbd.old file did not exist in Step 9. Step 14. Repeat Step 12. and Step 13. for all the numbers obtained in Step 11. Step 15. Run$FS_HOME/util/buildtaf -i. At the prompt, typeD to do it. Step 16. Start lockmgr: lm_start. Step 17
ملخص المحتوى في الصفحة رقم 15
Installing FileServ and AMASS on the Same Platform Step 1. If you have FileServ and AMASS on the same platform, start the FileServ processes before the AMASS processes (CR #1780). Step 2. If the autostart scripts are enabled for both FileServ and AMASS, run the FileServ autostart script before the AMASSautostart script. To accomplish this, assign a name to the FileServautostart script so it will start before the AMASS autostart script. An example of the FileServ and AMASSautostart script names i
ملخص المحتوى في الصفحة رقم 16
Contents of Version 4.2 OPERATING SYSTEMS ® IRIX 6.2, 6.5.4M, 6.5.5M, and 6.5.6M SPARC™ Solaris™ 2.6 and 7 NEW DRIVE SUPPORT Additional drives supported by this release of FileServ include the following: - Storage Technology 9840. - Sony GY-10. - Sony GY-2120. - Sony GY-8240 FIXED PROBLEMS The following table lists fixed problems: Operating Problem Description of Problems Fixed in Version 4.2 System Number All 427 If a file is stored, overwritten, renamed, and restored, the name is never upda
ملخص المحتوى في الصفحة رقم 17
Operating Problem Description of Problems Fixed in Version 4.2 System Number Solaris 467 The fsaddrelation command was not making the associations on Solaris. This has been fixed. All 468 The fsclean -c -t endtime command removed information from the trashcan at the wrong time. This has been fixed. FileServ Version 4.3—600726 Rev A Page 17 of 22 www.adic.com
ملخص المحتوى في الصفحة رقم 18
Contents of Version 4.1 OPERATING SYSTEMS Initial release of FileServ on IRIX 6.5.6. Support for Solaris 2.6 has been put back in FileServ. NEW DRIVE SUPPORT Additional drives supported by this release of FileServ include the following: - Fujitsu M8100. Configure this drive as an IBM 3590B1A. - Quantum DLT 8000. Configure this drive as a Quantum DLT 4000. AUTOMATIC DRIVE CLEANING (#218) Automatic drive cleaning has been added for the following drives: - Sony AIT-1 SDX-300 and AIT-2 SDX-5
ملخص المحتوى في الصفحة رقم 19
FIXED PROBLEMS The following table lists fixed problems: Operating Problem Description of Problems Fixed in Version 4.1 System Number All 173 Added logic to randomly retry database locks. All 177 Updated fspolicy man pages to describe the -v drivepool option. All 338 Made changes to install script to change emassadm to adicadm. All 342 Introduced device SCSI code into scm and fixed several problems with MO 352 drives. All 348 Fixed fsmedin man page and reference to MO5.25 for magneto optical dri
ملخص المحتوى في الصفحة رقم 20
Contents of Version 4.0 OPERATING SYSTEMS Initial release of FileServ on the following operating systems: - Solaris Version 7.0. > Supports Veritas Vxfs Version 3.3.2 (CR #334). - IRIX Version 6.5.4 and 6.5.5. FileServ no longer supports the following operating systems: - Solaris Version 2.6. - IRIX Versions 6.5, 6.5.2, and 6.5.3. DRIVE SUPPORT Initial support of the drives below. To update the system parameters to reflect the proper capacity, see “Updatesysparm File with Media Capacity” o
