test/blocktest/test.sh

   1 #!/bin/sh
   2
   3 # The blocktest driver expects the following parameters:
   4 #
   5 # device       Path to the device node to perform the test on. This may be a
   6 #              full disk, a partition, or a subpartition. If possible, give
   7 #              blocktest the whole disk; otherwise preferably the first
   8 #              partition with a size of slightly over 8GB (for ATA) (better
   9 #              yet: slightly over 128GB); even fewer tests can be done if you
  10 #              give it only a subpartition.
  11 # rw (or) ro   Specifying "rw" will let blocktest write to the target
  12 #              partition. This allows for a lot more tests, but keep in mind
  13 #              that any data on the partition (and, if the driver misbehaves,
  14 #              on other partitions and possibly other disks) WILL BE DESTROYED.
  15 #              Use "ro" for read-only mediums, such as CD-ROMs.
  16 # sector       Sector size, in bytes. This should be 512 for ATA devices, and
  17 #              2048 for ATAPI devices.
  18 # min_read     Minimum size of a read request. This must be at least 2 and at
  19 #              most the sector size, and the sector size must be divisible by
  20 #              it. A value other than the sector size allows blocktest to test
  21 #              sub-sector reads. Sub-sector writes are currently not supported
  22 #              by any driver and hence not by blocktest, so there is no
  23 #              matching "min_write" (yet).
  24 # element      Minimum size of a vector element within a larger I/O request.
  25 #              This must be at least 2 and at most min_read, and min_read must
  26 #              be divisible by this value. The idea is that several small
  27 #              elements may add up to the minimum read size.
  28 # max          Maximum size of any request. This should be a multiple of the
  29 #              sector size. Blocktest will not test what happens when this
  30 #              value is exceeded, but it will generate large requests up to
  31 #              this value. For drivers that do not have a maximum request size,
  32 #              simply use some large value (typically several megabytes).
  33
  34 # The following are examples of how to configure blocktest for certain driver
  35 # and device pairs. Before commenting out any entry, you MUST edit the "device"
  36 # option for that entry, or you WILL risk losing arbitrary data. You may run
  37 # multiple tests in parallel (on different devices), but you will then have to
  38 # give them different labels. Note that at_wini has no maximum request size, so
  39 # an arbitray size is used. Finally, a disclaimer: a buggy device driver may
  40 # destroy any data it has access to, so use at your own risk.
  41
  42 # AT_WINI ATA TEST (for IDE disk devices)
  43
  44 #service up `pwd`/blocktest -script /etc/rs.single -args "device=/dev/c0d1,rw,sector=512,min_read=512,element=2,max=16777216" -config system.conf -label blocktest_0
  45
  46 # AT_WINI ATAPI TEST (for IDE CD-ROM devices)
  47
  48 #service up `pwd`/blocktest -script /etc/rs.single -args "device=/dev/c0d2,ro,sector=2048,min_read=2,element=2,max=16777216" -config system.conf -label blocktest_0
  49
  50 # AHCI ATA TEST (for SATA disk devices)
  51
  52 #service up `pwd`/blocktest -script /etc/rs.single -args "device=/dev/c2d0,rw,sector=512,min_read=2,element=2,max=4194304" -config system.conf -label blocktest_0
  53
  54 # AHCI ATAPI TEST (for SATA CD-ROM devices)
  55
  56 #service up `pwd`/blocktest -script /etc/rs.single -args "device=/dev/c2d1,ro,sector=2048,min_read=2,element=2,max=4194304" -config system.conf -label blocktest_0