Encrypted Volume and File System v2.2 Administrator Guide (777846-001, April 2014)

The syntax of the evfsadm map command is as follows:
evfsadm map volume_path
where:
volume_path Specifies the absolute path of the block device file for the underlying LVM,
VxVM, or physical volume, such as /dev/vx/dsk/rootdg/vol01, /dev/
vg01/lvol5, or /dev/dsk/c2d0t0.
The evfsadm map command maps the underlying LVM, VxVM, or physical volume to an EVS
volume. The command also creates a block and a character () device file for the EVS volume and
adds them to the kernel registry. The evfsadm command stores the EVS volume device files using
the same file names as the underlying volume block and character device files, but in subdirectories
under the /dev/evfs directory instead of the /dev directory. Once the volume is mapped, access
to both the underlying volume path (/dev/disk) and the EVS volume path (/dev/evfs/disk)
is shared. HP recommends that you use the EVS volume path (for example, /dev/evfs/disk).
NOTE: The maximum number of volumes that the system can map to EVFS is 1023.
Examples
In the following example, the user maps the LVM volume /dev/vg01/lvol5 to an EVS volume:
# evfsadm map /dev/vg01/lvol5
Logical volume "/dev/vg01/lvol5" has been successfully mapped
to encrypted volume "/dev/evfs/vg0l/lvol5".
The evfsadm utility creates the following EVS volume device files:
/dev/evfs/vg01/lvol5
/dev/evfs/vg01/rlvol5
In the following example, the user maps the VxVM volume/dev/vx/dsk/rootdg/vol05 to an
EVS volume:
# evfsadm map /dev/vx/dsk/rootdg/vol05
Logical volume "/dev/vx/dsk/rootdg/vol05" has been successfully mapped
to encrypted volume "/dev/evfs/vx/dsk/rootdg/vol05".
The evfsadm utility creates the following EVS volume device files:
/dev/evfs/vx/dsk/rootdg/vol05
/dev/evfs/vx/rdsk/rootdg/vol05
In the following example, the user maps the physical volume /dev/dsk/c2t0d0 to an EVS
volume:
# evfsadm map /dev/dsk/c2t0d0
Logical volume "/dev/dsk/c2t0d0" has been successfully mapped to
encrypted volume "/dev/evfs/dsk/c2t0d0".
The evfsadm utility creates the following EVS volume device files:
/dev/evfs/dsk/c2t0d0
/dev/evfs/rdsk/c2t0d0
Step 1c: Creating the EMD
Use the evfsvol create command to create the EMD area on the EVS volume and specify the
owner key pair for the volume:
evfsvol create -k keyname [-c cipher]evfs_volume_path
where:
-k keyname Specifies the key pair name. The evfsadm utility creates the EMD area
with the keyname as the owner key. For information about user keys,
see “Creating keys” (page 41).
-c cipher Specifies the cipher (cryptography) algorithm EVFS uses to encrypt the
volume data.
Option 1: Creating a new EVS volume 47