This file is a compilation of the few various AppLabs text files found in the tarball. These are made as one text file for quick and easy online viewing. The text files which come with the testing programs themselves are in separate folders in the tarball. The various text files are separated with lines like: >>> BEGIN SCSI WORKSHEET <<< >>> END SCSI WORKSHEET <<< >>> BEGIN TTCP TEST TOOL TEXT FILE <<< >>> END TTCP TEST TOOL TEXT FILE <<< The text files included in this file are: scsi_cert.txt bonnie_test.txt If you have questions you can direct them to linux@applabs.com. >>> BEGIN SCSI WORKSHEET TEXT <<< SCSI Adapter Worksheet AppLabs' SCSI Adapter Certification Test, Revision 1.5 - JCW Tester's Name: ___________________________________________ Date:______________ Section 1: Product Information Manufacturer: _________________________________________________________________ Product Name and Model Number: ________________________________________________ Product Description: __________________________________________________________ Overall Result: Pass Fail Details: ______________________________________________________________________ Section 2: Setup Information Distributions Tested: Version: Result: [ ] Caldera _____________ Pass Fail [ ] Pacific High Tech _____________ Pass Fail [ ] S.u.S.E. _____________ Pass Fail [ ] Redhat _____________ Pass Fail Describe Test System Hardware: ________________________________________________ Describe Test System's Onboard HD Capabilities: _______________________________ Section 3: Tests Card Detection Test: Pass Fail Low-Level Format Test: Pass Fail N/A Driver Installation Test: Pass Fail Format Test: Pass Fail Bottleneck Test, stats collected? Yes No Multiple Device Test: Pass Fail N/A Multiple Cards/Drives Test: Pass Fail N/A Software RAID Test: Pass Fail Section 4: Test Procedures Card Detection Test Procedure: Tester makes a fresh install of the Linux distribution being tested against and verifies the install procedure detects the controller card or allows the tester to specify the presence of the specific SCSI controller card. Testers must be sure to do either a complete install or a server-type install since server load testing of the controller/drive/CPU is used later in this cert. Determination: If the install software makes it possible, either automatically or manually, for the install procedure to correctly identify the controller card, the test is a pass. If the install software does not detect the presence of a SCSI controller card or does not allow the installer/tester to specify a SCSI controller card, the test is a fail against that particular Linux distribution. Low-level Format Test Procedure: During boot up, the tester enters CMOS/BIOS and uses the low-level format utility to format the drive. Determination: If the format successfully completes the format, the test is a pass; otherwise, if the format returns errors related to the formatting of the drive or otherwise ends prematurely, the test is a fail. Driver Installation Test Procedure: Tester verifies the install software identifies and installs the correct driver or allows the tester to select the correct driver for the controller card. During an install, this will usually involve selecting a pre-compiled kernel with the SCSI driver either installed or built as a module. Determination: If the install software installs the correct driver or otherwise allows the tester to select and install the correct driver manually, the test is a pass. If the install software does not install the correct driver or does not allow the tester to select the correct driver, the test is a fail. Fdisk/Partitioning Test Procedure: Tester uses Gnu fdisk to partition the SCSI fixed drive. Tester is to make one swap partition and two native Linux partitions, then write the information to disk. Determination: If no errors are reported, the partition table shows correct block numbers, and the new information about the partitions is successfully written to disk, the test is a pass. If 1) any errors are returned by the fdisk program (which cannot be attributed to tester error); or, 2) the partition table shows obvious errors such as incorrect block numbers, over-lapping block numbers, etc. then the test is a fail. Format Test Procedure: Tester instructs and observes the install process in the formatting of the new partitions. Determination: If the install software reports successful formatting or begins installation of the software packages, the test is a pass. If any errors are reported or the install aborts, the test is a fail. Bottleneck Test Procedure: Using the bonnie test program, the tester collects performance statistics on the card/drive/CPU. These statistics should be presented for the customer and their potential customers to view. The statistics should be presented in the same format as is shown in the bonnie README file. Determination: This is not a pass/fail test, but information for potential\ users to view. Multiple Device Test Procedure: Connect two or more SCSI devices to the system via the same adapter. Determination: If the various SCSI devices work well with the system then the test is a pass. If the two devices cannot be made to work simultaneously then the test is a fail. Multiple Card/Drives Test Procedure: Connect two SCSI adapter cards, each with its own separate hard drive. Using the bonnie load test program, collect test statistics and compare with the manufacturer's promotional statistics. Determination: If the two sets of figures are comparable (without large differences between the two sets of figures) the test is a pass. If the two sets of figures are not similar in times and speeds, the test is a fail. Software RAID Test Procedure: Tester sets up a software RAID system using two or more SCSI drives on one SCSI adapter. Determination: If the drives format and perform as expected according to the Root-RAID- HOWTO the test is a pass. If the drives cannot be made to format and work in a RAID format the test is a fail. References: 1. README.aic7xxx - Driver README for the kernel used in testing. Located where the source code for drivers is stored, usually in a directory called Documentation. 2. SCSI-HOWTO (plenty of detail for trouble shooting setups, etc.) 3. Hardware-HOWTO (list of supported hardware, etc.) 4. Kernel-HOWTO (getting the driver into the kernel or a module, working with the kernel). 5. Large-Disk-mini-HOWTO (may be of some use in certain testing situations). 6. Root-Raid-HOWTO >>> END SCSI WORKSHEET TEXT <<< >>> BEGIN BONNIE TEST TEXT <<< bonnie_test.txt for AppLabs Test Packages Bonnie is a file system benchmarking utility. It is used for identifying and measuring file system bottlenecks. It is also useful for stress testing the file system since it can put a heavy load on a file system. Using bonnie ------------ Steps: 1. Put bonnie in your path (/usr/local/bin/ is good) 2. Set the BONNIESIZE variable (see below) 3. Execute the run-bonnie script Steps Explained --------------- To use bonnie you'll first want to make sure bonnie is somewhere in the path so the system can find and run it. One of the common bin directories is good (/usr/local/bin/) or your personal bin directory (~/bin/) will work too. The run-bonnie script, obviously, requires the bonnie disk test to be installed and in the path. The run-bonnie script is a simple script to file used to run the "bonnie" disk test over and over. You need to set up the BONNIESIZE environment variable before running this script. Multiply the ammount of system memory by 2.5 and execute tne following, wnere n equals your desired test size: export BONNIESIZE=n You can check the BONNESIZE variable with this command: echo $BONNIESIZE If you have problems getting bonnie or run-bonnie to run, check permissions on the two files: Both must be executable. Bonnie will return some information about each test. See the man page for specifics about the output contents and format. >>> BEGIN BONNIE TEST TEXT <<<