SCSI Certification Requirements and Procedures
(rev .11)
September 9 1999
| CARD DETECTION |
Procedure Make a fresh install of the Linux distribution being tested, and verify the install procedure detects the controller card or allows the tester to specify the presence of the specific SCSI controller card. Be sure to do either a complete install or a server-type install since server load testing of the drive/controller/CPU is used later in this cert. | Pass If the install software does make it possible , either automatically or manually, for the install procedure to correctly identify the controller card, the test must be listed as a pass. Fail If the install software does not detect the presence of a SCSI controller card or does not allow the installer to specify a SCSI controller card, the test must be listed as a failure against that distribution. |
| DRIVER INSTALLATION |
Procedure After the controller card is detected in the previous test , verify the install software identifies and installs the correct driver or allows the tester to select the correct driver for the controller card. During the install, this will usually involve selecting a pre-compiled kernel with the SCSI driver either installed or built as a module | Pass If the install software installs the correct driver of allows the tester to select and install the correct driver manually, the test must be listed as a pass. Fail If the install software does not install the correct driver or allow the tester to select the correct driver, the test must be listed as a failure against the distribution. |
| DRIVE PREP |
Procedure During the install process, the tester is to use Gnu fdisk(the install process will present an opportunity) to partition the SCSI fixed driver. Make one swap partition and two Linux partitions, then write the information to disk. | Pass If no errors are reported, the partition table shows apparently correct blocknumbers and the new information about the partitions is successfully written to disk, the test must be listed as a pass.
Fail If any errors are returned by the fdisk program, which cannot be determined to be user error, the test must be listed as a fail. If the partition table shows obvious errors such as incorrect block numbers, over-lapping block numbers, etc. the test must be listed as a fail. |
| FORMAT TEST |
Procedure The tester is to instruct and observe the install process in the formatting of the new partitions. | Pass If the install software reports successful formatting or begins install of the software package the test is a pass.
Fail If any errors are reported, the test must be listed as a fail. |
| BOTTLENECK TEST |
Procedure Use the bonnie test program to collect performance statistics of the card/drive/cpu. These statistics should be presented with the final report. The statistics should be presented in the format that is shown in the Bonnie README file. This is not a PASS/FAIL test. |
| MULTIPLE DEVICE TEST |
Procedure Connect two or more SCSI devices to the system simultaneously via the same adapter. | Pass If the various SCSI devices work well with the system then the test is a pass
Fail If the two devices cannot be made to work simultaneously then the test must be listed as a fail. |
| MULTIPLE CARD/DRIVES TEST |
Procedure Connect two SCSI adapter cards each with its own separate hard drive. Using the Bonnie load test modules, collect test statistics and compare with manufacturer's statistics.
| Pass If the two sets of figures are comparable and without large differences, then the test is a pass.
Fail If the two sets of figures (bonnie and manufacturer) are not similar in times and speeds, then the test must be listed as a fail.. |
| SOFTWARE RAID TEST |
Procedure Setup a software RAID system using two or more SCSI drives on one SCSI adapter.
| Pass If the drives format and work as expected according to the root-RAID-HOWTO Document, the test is a pass.
Fail If the drives cannot be made to format and work in the RAID array, the test must be listed as a fail. |
|