scsa1394(7D)							      Devices							      scsa1394(7D)

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(7D).

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

       In  previous  releases, all 1394 mass storage devices were treated as removable media devices and managed by rmformat(1) and volume manage-
       ment 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 with-
       out 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(1M) and mount(1M) 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 soft-
       ware 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(4). See the System Administration Guide, Volume  I  and  Solaris  Common
       Desktop Environment: User's Guide for details on how to manage a removable device with CDE and Removable Media Manager. See dtfile.1X under
       CDE for information on how to use Removable Media Manager.

USING mount AND umount
       Use mount(1M) to explicitly mount the device and umount(1M) to unmount the device. Use eject(1) to eject the media. After you have  explic-
       itly 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.

       For a comprehensive listing of (non-bootable) 1394 mass-storage devices that are compatible with this driver, see www.sun.com/io.

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(7D).

IOCTLS

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

ERRORS

       Refer to sd(7D).

FILES

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

       /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

       See attributes(5) for a description of the following attributes:

       +-----------------------------+------------------------------+
       |ATTRIBUTE TYPE		     |ATTRIBUTE 		   VALUE
       +-----------------------------+------------------------------+
       |Architecture		     |SPARC, x86, PCI-based systems |
       +-----------------------------+------------------------------+
       |Availability		     |SUNWscsa1394		    |
       +-----------------------------+------------------------------+

SEE ALSO

       cdrw(1), eject(1), rmformat(1), rmmount(1), cfgadm_scsi(1M), fdisk(1M), mount(1M), umount(1M),  dtfile.1X  (in  CDE  man  pages),  scsi(4),
       vfstab(4), attributes(5), hci1394(7D), sd(7D), pcfs(7FS), cdio(7I), dkio(7I)

       IEEE Std 1394-1995 Standard for a High Performance Serial Bus

       ANSI NCITS 325-1998 - Serial Bus Protocol 2 (SBP-2)

       System Administration Guide: Devices and File Systems

       SCSI Specification T10/995D Revision 11a -- March 1997

       SCSI SpecificationT10/1236-D Revision 20 -- July 2001

       SCSI SpecificationT10/1416-D Revision 23-- May 2005

       Solaris Common Desktop Environment: User's Guide

       http://www.sun.com/io

SunOS 5.11							    2 Mar 2007							      scsa1394(7D)