HP DDS/DAT tape drives UNIX, Linux and OpenVMS configuration guide (DW049-90930, May 2010)

MeaningValueParameter

YesNoDevice determines which of the two

mode pages the device supports for

selecting or deselecting compression.

0x10000

There is one density code following in the parameter list.1<no. of

densities>

Supported density code. The value of 0x00 means use the default density chosen

by the drive—which is 0x26 for DDS-4, 0x47 for DAT 72, 0x48 for DAT 160

and 0x4D for DAT 320.

0x26,

0x47,

0x48,

0x4D or

0x00

Density 0 (0x26 for DDS-4, 0x47 for DAT 72, 0x48 for DAT 160, 0x4D for

DAT 320) is the default.

0<default

density>

All timeouts are in seconds<X timeout>

Values for the parameters for name are as follows:

MeaningValueParameter

X specifies the SCSI ID (target) of the device.Xtarget

Specifies the LUN for the device.

0lun

SAS drives

Identifying attached devices

Use the cfgadm command to list attached tape devices:

% cfgadm -al |grep tape

This produces output lines with a format similar to the following:

c9::rmt/0 tape connected configured unknown

The rmt/K entry indicates the tape device file, where K is the instance number. In the above example,

rmt/0 indicates a set of device file options for one tape drive, such as /dev/rmt/0cb, /dev/rmt/

0cbn, and so on.

The cfgadm command may also be used with the –v (verbose) option to list a full path including the

SAS controller:

% cfgadm -val |grep tape

An output containing, for example, “/devices/pci@0/pci@0/pci@8/pci@0/pci@1/

LSILogic,sas@0:scsi::rmt/1” indicates an SAS tape drive connected via an LSI SAS HBA.

Device file variants for a given tape device are listed in /dev/rmt with various suffixes—l, m, h, u, c specifying the ‘density’

(low, medium, high, ultra, compressed), plus additional options b, ‘Berkeley’ behavior, and n, no rewind behaviour. HP

recommends the ‘Berkeley’ device file option for most applications with compressed density c: /dev/rmt/0cb or /dev/rmt/

0cbn

Sun (Solaris) servers and workstations36