Tribblix: manual page: scsa1394.4d

SCSA1394(4D) Devices SCSA1394(4D)

NAME

scsa1394 - SCSI to 1394 bridge driver

SYNOPSIS

unit@GUID

DESCRIPTION

The scsa1394 driver is a 1394 target and an SCSA HBA driver that
supports 1394 mass storage devices compliant with the Serial Bus
Protocol 2 (SBP-2) specification. It supports both bus-powered and
self-powered 1394 mass storage devices.

The scsa1394 nexus driver maps SCSA target driver requests to SBP-2
Operation Request Blocks (ORB's).

The scsa1394 driver creates a child device info node for each logical
unit (LUN) on the mass storage device. The standard Solaris SCSI disk
driver is attached to those nodes. Refer to sd(4D).

This driver supports multiple LUN devices and creates a separate
child device info node for each LUN. All child LUN nodes attach to
sd(4D).

In previous releases, all 1394 mass storage devices were treated as
removable media devices and managed by rmformat(1) and volume
management software. In the current release, however, only mass
storage devices with a removable bit (RMB) value of 1 are removable.
(The RMB is part of the device's SCSI INQUIRY data.) See SCSI
specifications T10/995D Revision 11a, T10/1236-D Revision 20 or
T10/1416-D Revision 23 for more information. However, for backward
compatibility, all 1394 mass storage devices can still be managed by
rmformat(1). With or without a volume manager, you can mount, eject,
hot remove and hot insert a 1394 mass storage device as the following
sections explain.

USING VOLUME MANAGEMENT

Mass storage devices are managed by a volume manager. Software that
manages removable media creates a device nickname that can be listed
with eject(1) or rmmount(1). A device that is not mounted
automatically can be mounted using rmmount(1) under /rmdisk/label.
Note that the mount(8) and mount(8) commands do not accept nicknames;
you must use explicit device names with these commands.

See rmmount(1) to unmount the device and eject(1) to eject the media.
If the device is ejected while it is mounted, volume management
software unmounts the device before ejecting it. It also might kill
any active applications that are accessing the device.

Volume management software is hotplug-aware and normally mounts file
systems on USB mass storage devices if the file system is recognized.
Before hot removing the USB device, use eject(1) to unmount the file
system.

You can disable the automatic mounting and unmounting of removable
devices by inserting a entry for a removable device in /etc/vfstab.
In this entry, you must set the mount at boot field to no. See
vfstab(5).

USING mount AND umount
Use mount(8) to explicitly mount the device and umount(8) to unmount
the device. Use eject(1) to eject the media. After you have
explicitly mounted a removable device, you cannot use a nickname as
an argument to eject.

Removing the storage device while it is being accessed or mounted
fails with a console warning. To hot remove the storage device from
the system, unmount the file system, then kill all applications
accessing the device. Next, hot remove the device. A storage device
can be hot inserted at any time.

DEVICE SPECIAL FILES

Block special file names are located in /dev/dsk. Raw file names are
located in /dev/rdsk. Input/output requests to the devices must
follow the same restrictions as those for SCSI disks. Refer to
sd(4D).

IOCTLS

Refer to cdio(4I) and dkio(4I).

ERRORS

Refer to sd(4D).

FILES

The device special files for the 1394 mass storage device are created
like those for a SCSI disk. Refer to sd(4D).

/dev/dsk/cntndnsn

Block files

/dev/rdsk/cntndnsn

Raw files

/vol/dev/aliases/rmdisk0

Symbolic link to the character device for the media in removable
drive 0. This is a generic removable media device.

/kernel/drv/scsa1394

32-bit x86 ELF kernel module

/kernel/drv/amd64/scsa1394

64-bit x86 ELF kernel module

/kernel/drv/sparcv9/scsa1394

64-bit SPARC ELF kernel module

ATTRIBUTES