Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ sd(7) — sysv — mips UMIPS RISC/os 4.52

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

common_scsi(7)

dvhtool(1M)

prtvtoc(1M)

dvh(4)



SD(7-SysV)          RISC/os Reference Manual           SD(7-SysV)



NAME
     sd - Rx2030 IOP SCSI disk and tape controller interface

DESCRIPTION
     This is a driver for the Rx2030 IOP SCSI disk and tape con-
     troller and interfaces with the common_scsi(7) driver.  The
     standard disk device names are in the /dev/dsk directory and
     begin with ``sdc0d'' followed by the drive number 0-6 and
     then the letter ``s'' followed by the partition number 0-15.
     The minor device numbers for disks are ``16 * drive_number +
     partition''.  For example, drive 1, partition 6 would be
     designated ``sdc0d1s6'' and have a minor device number of
     22.

     Tape devices have two types of operation associated with
     each drive.  The rewind device will rewind the tape on close
     while the no rewind device does not change the tape position
     on close.  The standard device names for tape devices are
     based on the type of tape.  Cartridge tapes are historically
     called ctape0 and ctape4 for the rewind and no rewind dev-
     ices respectively. Half-inch tape drives are called h0 and
     h4 for the rewind and no rewind devices respectively. High
     capacity 8mm tape drives are called hc0 and hc4 for the
     rewind and no rewind devices respectively. The minor device
     numbers for tapes are ``16 * drive_number + no_rewind''.
     For example, cartridge tape drive 6, rewind on close, would
     be designated ``ctape0'' and have a minor device number of
     96. The no-rewind name would be ``ctape4'' and have a minor
     number of 97.  Cartridge tapes are normally assigned to
     drive 6, half-inch tapes to drive 5 and high-capacity 8mm
     tapes to drive 4.  Tape devices are always character dev-
     ices.

     The block files access the disk via the system's normal
     buffering mechanism and may be read and written without
     regard to physical disk records.  There is also a "raw"
     interface that provides for direct transmission between the
     disk and the user's read or write buffer.  A single read or
     write call results in exactly one I/O operation and there-
     fore raw I/O is considerably more efficient when many words
     are transmitted.  The names of the raw files are the same as
     the standard disk device names described above but are con-
     ventionally in the /dev/rdsk directory.

     In raw I/O, buffers should be page aligned for best perfor-
     mance and I/O counts should be a multiple of the device
     block size (512 bytes for a disk sector) or the exact record
     size for variable record devices.  Reads of less than the
     device block size are allowed if the request begins on a
     block address. Writes of less than the device block size
     will write undefined data for the remainder of the block.
     Likewise seek calls should specify a multiple of the device



                         Printed 1/28/91                   Page 1





SD(7-SysV)          RISC/os Reference Manual           SD(7-SysV)



     block size.  Seek calls to a non-block aligned address will
     cause the next read to fail.

     Disk volumes on MIPS computers systems contain a volume
     header that describes the contents of the disk and parame-
     ters of the physical disk drive.  The volume header is a
     block located at the beginning of all disk media.  It con-
     tains information about physical device parameters and logi-
     cal partition information.  Refer to dvh(4) for details on
     the disk volume header format.  Volume headers are created
     by formatters and may be manipulated by dvhtool(1M) via the
     special raw device ``/dev/rdsk/sdc0d?vh'' where ? is the
     drive number 0-6.  Another special raw device exists,
     ``/dev/rdsk/sdc0d?s10'', for use by formatters to access the
     entire disk volume.

FILES
     /dev/[r]dsk/sdc0d[0-6]s[0-15]
     /dev/rdsk/sdc0d[0-6]vh
     /dev/rmt/ctape0
     /dev/rmt/ctape4
     /dev/rmt/h0
     /dev/rmt/h4
     /dev/rmt/hc0
     /dev/rmt/hc4

SEE ALSO
     common_scsi(7), dvhtool(1M), prtvtoc(1M).
     dvh(4) in the Programmer's Reference Manual.

DIAGNOSTICS
     See also the diagnostics described in common_scsi(7).

     V50 PROM version number %d

          During initialization, if showconfig is set, the ver-
          sion number of the V50 PROM is displayed.

     PANIC: Invalid group code: command = 0x%x

          If the SCSI command is an invalid group code, the sys-
          tem panics. The offending command code is printed.

     SCSI %dL%d: POLLED timeout

          A polled command (used during system startup) has timed
          out.

     SCSI %d: cmd timed out/semaphore set

          UNIX has timed out waiting for an interrupt from the
          IOP, however the status semaphore is set indicating an



 Page 2                  Printed 1/28/91





SD(7-SysV)          RISC/os Reference Manual           SD(7-SysV)



          interrupt should have been generated.

     SCSI %d: cmd timed out - resetting SCSI bus

          UNIX has timed out waiting for an interrupt from the
          IOP. The SCSI bus will be reset to attempt error
          recovery.

     PANIC: SCSI %d: SHA_RESET cmd timed out

          An attempt to reset the SCSI bus has failed.

     SCSI %d: no timeout set

          An interrupt has been received for a command block that
          had no timeout set.







































                         Printed 1/28/91                   Page 3



Typewritten Software • bear@typewritten.org • Edmonds, WA 98026