Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

scsi(4) [ultrix man page]

SCSI(4) 						     Kernel Interfaces Manual							   SCSI(4)

Name
       SCSI - Small Computer System Interconnect

Description
       The  ULTRIX  system interfaces to disk and tape devices through the Small Computer System Interconnect (SCSI).  Initial ULTRIX SCSI support
       is limited to the Digital-supplied mass storage devices.  The following devices are fully supported on the ULTRIX system:

       o    Winchester disks: RZ22, RZ23, RZ23L, RZ24, RZ55, RZ56, RZ57, RX23, RX26, RX33

       o    Magnetic tapes: TZ30, TZK50, TLZ04, TSZ05, TKZ08, TZK10

       o    Optical disks: RRD40, RRD42

       Under the ULTRIX operating system, a SCSI device is referred to by its logical name.  Logical names take the following form:
       nn#
       The nn argument is the two-character name; the number sign (#) represents the unit number.  The two character names for SCSI devices are:

       rz  -  RZ22, RZ23, RZ23L, RZ24, RZ55, RZ56, RZ57, RX23, RX26, RX33, RRD40, RRD42 disks

       tz  -  TZ30, TZK50, TLZ04, TSZ05, TKZ08, and TZK10 tapes

       The unit number is a combination of the SCSI bus number, either 0, 1, ... and the device's target ID number.   The  unit  number  is  eight
       times  the  bus	number plus the target ID.  For example, an RZ23 disk at target ID 3 on bus 0 would be referred to as rz3; a TZK50 tape at
       target ID 5 on the second SCSI bus would be referred to as 13.

       The SCSI bus has eight possible target device IDs.  By default, one is allocated to the system.	This allows for a maximum of seven  target
       devices connected to a SCSI bus.

Restrictions
       The ULTRIX SCSI device driver does not operate with optical disks, other than the Digital-supplied devices.

       The SCSI driver attempts to support on a best effort basis, non-Digital-supplied winchester disks and magnetic tapes.

       The following notes apply to the driver's handling of non-Digital-supplied disks:

	  o   These disks are assigned a device type of RZxx, instead of RZ22, RZ23, RZ23L, RZ55, RZ56, RZ57, RX23, RX26, or RX33.  The RZxx disks
	      follow the same logical device naming scheme as the Digital-supplied disks.

	  o   During the autoconfigure phase of the system startup, the driver prints the contents of the SCSI vendor  ID,  product  ID,  and  the
	      revision level fields of the inquiry data return by the SCSI device.

	  o   RZxx  disks  are	assigned a default partition table. The default table can be modified by editing the sz_rzxx_sizes[8] entry in the
	      file The utility can also be used to modify the partition table on a RZxx disk.

	  o   The only logical unit number (LUN) supported for each target ID is 0.

See Also
       rz(4), tz(4), chpt(8)

																	   SCSI(4)

Check Out this Related Man Page

tran_reset(9E)							Driver Entry Points						    tran_reset(9E)

NAME
tran_reset - reset a SCSI bus or target SYNOPSIS
#include <sys/scsi/scsi.h> int prefixtran_reset(struct scsi_address *ap, int level); INTERFACE LEVEL
Solaris architecture specific (Solaris DDI). PARAMETERS
ap Pointer to the scsi_address(9S) structure. level The level of reset required. DESCRIPTION
The tran_reset() vector in the scsi_hba_tran(9S) structure must be initialized during the HBA driver's attach(9E) to point to an HBA entry point to be called when a target driver calls scsi_reset(9F). tran_reset() must reset either the SCSI bus, a SCSI target device, or a SCSI logical unit as specified by level. level must be one of the following: RESET_ALL Reset the SCSI bus. RESET_TARGET Reset the target specified by ap. RESET_LUN Reset the logical unit specified by ap. tran_reset should set the pkt_reason field of all outstanding packets in the transport layer associated with each target or logical unit that was successfully reset to CMD_RESET and the pkt_statistics field must be OR'ed with either STAT_BUS_RESET (if the SCSI bus was reset) or STAT_DEV_RESET (if the target or logical unit was reset). The HBA driver should use a SCSI Bus Device Reset Message to reset a target device. The HBA driver should use a SCSI Logical Unit Reset Message to reset a logical unit. Packets that are in the transport layer but not yet active on the bus should be returned with pkt_reason set to CMD_RESET and pkt_statis- tics OR'ed with STAT_ABORTED. Support for RESET_LUN is optional but strongly encouraged for new and updated HBA drivers. If an HBA driver provides RESET_LUN support, it must also create the lun-reset capability with a value of zero for each target device instance represented by a valid ap. The HBA is also required to provide the means to return the current value of the lun-reset capability in its tran_getcap(9E) routine, as well as the means to change the value of the lun_reset capability in its tran_setcap(9E) routine. RETURN VALUES
tran_reset() should return: 1 on success. 0 on failure. SEE ALSO
attach(9E), ddi_dma_buf_setup(9F), scsi_hba_attach(9F), scsi_reset(9F), scsi_address(9S), scsi_hba_tran(9S) Writing Device Drivers NOTES
If pkt_reason already indicates that an earlier error had occurred for a particular pkt, tran_reset() should not overwrite pkt_reason with CMD_RESET. SunOS 5.10 12 Jul 2002 tran_reset(9E)
Man Page