
38 SVA Path User’s Guide
SVA Path installations, SVA Path creates a single additional
device filename for applications to access the device and manages
the original device files transparently to those applications.
Note: It is the virtual device file that will be used by applications
to access that device. The original, redundant data paths should
never be used to access the device, or the data it contains could be
corrupted.
For example, an SVA might present a single physical disk device
to the HP-UX host as
c1t0d0 and c2t0d0. SVA Path creates a
third device file named c81t0d0 that is used by applications to
access the storage. It blocks applications’ access to the original two
device files.
How Device
Filenames Are
Chosen
In order to provide interoperability with complementary storage
management software (e.g., Logical Volume Manager), SVA Path
uses standard HP-UX device names in the form
cXtYdZ, where X
represents a controller or HBA number, Y represents a SCSI target
number, and
Z represents a SCSI LUN.
When SVA Path adds new device files to the system and changes
the device names by which pre-existing devices must be accessed,
the new device files, in order to be as easily understood as
possible, retain the SCSI target and LUN from the original device
files.
For example, a set of physical devices might originally be
accessible via HBAs
c1 and c2. SVA Path will create new, virtual
disk device files whose names start with
c81 and which have the
same target and LUN numbers as the original device files.
Therefore, a device originally accessible via the fibre channel or
SCSI disk driver device files c1t4d0 and c2t4d0 will, after SVA
Komentáře k této Příručce