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 RAID WORKSHEET <<<
>>> END RAID WORKSHEET <<<
>>> BEGIN TTCP TEST TOOL TEXT FILE <<<
>>> END TTCP TEST TOOL TEXT FILE <<<

The text files included in this file are:

raid_cert.txt
bonnie_test.txt

If you have questions you can direct them to linux@applabs.com.


>>> BEGIN RAID WORKSHEET TEXT <<<

RAID Storage Device Worksheet
AppLabs' RAID Device Certification Test, Rev. 1.1 - 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: _______________________________

RAID Device is: [ ]  internal to test system
                [ ]  separate component

Describe PCI/SCSI adapters used: ______________________________________________

Describe hard disks used:

Total number of hard disks used in test configuration: ________________________


Section 3: Tests

Tests Common to all RAID variations
  Configuration Tests
   RAID 0:                       Pass   Fail
   RAID 1:                       Pass   Fail
   RAID 5:                       Pass   Fail
  Mixed Array Test:              Pass   Fail   N/A
   
RAID 0 Tests
   Install Distribution:
     Adapter Detection:          Pass   Fail
     Logical Device Detection:   Pass   Fail
   Bonnie Stress:                Pass   Fail
   Dynamic Disk Removal:         Pass   Fail
   Static Disk Removal:          Pass   Fail

RAID 1 Tests
   Install Distribution:
     Adapter Detection:          Pass   Fail
     Logical Device Detection:   Pass   Fail
   Bonnie Stress:                Pass   Fail
   Dynamic Disk Removal:         Pass   Fail
   Static Disk Removal:          Pass   Fail
   Failed Disk:                  Pass   Fail

RAID 5 Tests
   Install Distribution:
     Adapter Detection:          Pass   Fail
     Logical Device Detection:   Pass   Fail
   Bonnie Stress:                Pass   Fail
   Dynamic Disk Removal:         Pass   Fail
   Static Disk Removal:          Pass   Fail
   Failed Disk:                  Pass   Fail



Section 4: Test Procedures


Configuration Tests

Procedure: Tester configures a RAID array for each type of RAID test to be
done against the system.

Determination: If the system properly configures the RAID system and reports
it ready for use, the test is a pass; otherwise, fail.  


Mixed Array Test

Procedure: Tester configures two different types of RAID systems on the same
system.

Determination: The system must allow at least two different types of logical
RAID logical drives to exist at the same time.


Distribution Install, Adapter Detection Test

Procedure: Tester verifies the Linux distribution correctly detects and loads
drivers for the SCSI adapter or adapters used in the system.

Determination: If the Linux distribution fails to properly detect the SCSI
adapters or fails to load the correct drivers, the test is a fail.


Distribution Install, Logical Device Detection Test

Procedure: Tester verifies the Linux distribution correctly detects any and
all types of RAID logical devices used in the Mixed Array test above.  The
distribution must detect both at the same time to pass, otherwise fail.


Bonnie Disk 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.


Dynamic Disk Removal & Replace Test

Procedure: After the Linux distribution has been installed and verified to be
working correctly (reboot after install), the tester removes one of the hard
disks while the system is running.

Determination: The system must behave according to the following per RAID #:

   RAID 1: System must continue to operate.  When the disk is returned into
           the system, the system must begin to rebuild the replaced disk.

   RAID 5: System must continue to operate.  When the disk is returned into
           the system, the system must begin to rebuild the replaced disk.


Static Disk Removal & Replace Test

Procedure: After the Linux distribution has been installed and verified to be
working correctly (reboot after install), the tester removes one of the hard
disks while the system is powered down.

Determination: The system must behave according to the following per RAID #:

   RAID 1: System must boot properly and completely to running status.  The
           system should then be powered down, the disk replaced and when
           the system is again powered up it must begin to rebuild the
           replaced disk.

   RAID 5: System must boot properly and completely to running status.  The
           system should then be powered down, the disk replaced and when
           the system is again powered up it must begin to rebuild the
           replaced disk.


Failed Disk Test

Procedure: The tester removes a drive from the running system and replaces it
           with a new hard disk.

Determination: The system must continue operating and must begin rebuilding the
           new disk upon its insertion into the system.

   
>>> END RAID 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.


>>> END BONNIE TEST TEXT <<<