Encrypted Volume and File System v1.1 Administrator's Guide

Description
The evfsvol create command fails if an EMD already exists on the volume. This can occur
if you reuse an EVFS volume without destroying the previous EMD.
Solution
If you are reusing an EVFS volume and do not want to recover the existing data, re-enter the
evfsvol create command with the -f option. The evfsvol create command generates
a new volume encryption key and new EMD. Any existing data is irrecoverable.
If you want to retrieve data from an existing EVFS volume and have problems with the existing
EMD, use the procedure described in “Recovering from EMD Corruption” (page 89).
evfsvol disable Fails, EVFS Volume Is Busy
Symptom
The evfsvol disable command returns the following error:
evfsvol: disable error: cannot disable encrypted volume
“evfs_volume_path”, evol is busy
Description
EVFS does not disable an EVFS volume if the volume is in use.
Solution
Terminate any processes that are accessing the volume. You can use the fuser -cu command
to determine the processes accessing files, and the fuser -cku command to terminate the
processes. See fuser(1M) for more information.
If the data is used by system processes, you might need to terminate the processes by changing
the system runlevel to single-user level with the shutdown utility. See shutdown(1M) for more
information.
If the volume has a file system mounted, unmount the file system. See umount(1M) for more
information.
evfsadm map Fails, Invalid Device
Symptom
The evfsadm map command returns the following error:
evfsadm: map error: invalid volume block device “filename”
For example:
evfsadm: map error: invalid volume block device “/dev/vg01/rlvol5”
Description
The command evfsadm map requires the name of a volume block device file as input. The
evfsadm utility maps the volume block device file to EVFS and automatically maps the
corresponding volume character (raw) device file to EVFS.
Solution
Specify a valid volume block device file. In the previous example, the user must replace
/dev/vg00/rlvol5 with /dev/vg00/lvol5.
Problem Scenarios 137