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 STORAGE WORKSHEET <<< >>> END STORAGE WORKSHEET <<< >>> BEGIN TTCP TEST TOOL TEXT FILE <<< >>> END TTCP TEST TOOL TEXT FILE <<< The text files included in this file are: storage_cert.txt >>> BEGIN STORAGE WORKSHEET <<< Storage Device Worksheet AppLabs Storage Device Certification Test, Revision 1.4 - JCW Tester's Name: _________________________________ Date: ______________ Section 1: Product Information Manufacturer: ________________________________________________________ Product Name and Model Number: _______________________________________ Product Description: _________________________________________________ Interface type: IDE SCSI Parallel USB Other: _______________ Capacity in MB/GB: __________ Overall Resutl: Pass Fail Details: _____________________________________________________________ Section 2: Setup Information Distributions Tested: Version: Result: [ ] Caldera _____________ Pass Fail [ ] TurboLinux _____________ 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 Drive Detection Test: Pass Fail Driver Installation Test: Pass Fail Partitioning Test: Pass Fail Format Test: Pass Fail File Integrity Test: Pass Fail Bonnie Load Test: Yes No Time test ran: _______ Section 4: Test Procedures Drive 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 controller card. Tester 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 controller card or does not allow the installer/tester to specify a controller card, the test is a fail against that particular Linux distribution. 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 or storage device. During an install, this will usually involve selecting a pre-compiled kernel with the appropriate 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 against that particular Linux distribution. Partitioning Test Procedure: Tester uses Gnu fdisk to partition the storage device media. 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 or manually makes a file system using mkfs. 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. If mkfs successfully completes the making of a file system on the media being tested and fsck reports no problems with the file system, the test is a pass; otherwise, fail. File Intregity Test Procedure: Tester makes a file on the test system's onboard disk drive. File size should be a minimum of one quarter the size of the media capacity of the storage device. Tester then copies this file to the storage media being tested. Tester then uses the cmp command to compare the two files. Determination: The cmp command must not report differences in the files for a pass; otherwise, fail. Bonnie Load Test Procedure: Using the bonnie test program setup, the tester collects performance statistics on the card/drive/CPU. The test should run for one hour minimum with statistics collected in a file and presented to 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. Bonnie output can be redirected into a file using this pattern: #: ./run-bonnie > bonnie_capture_file.txt 2>&1 Determination: This is not a pass/fail test, but information for potential users to view. 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. ZIP Drive Mini-HOWTO (useful when working with Iomega products.) >>> END STORAGE WORKSHEET <<< If you have questions you can direct them to linux@applabs.com.