Encrypted Volume and File System v2.2 Release Notes (777845-001, April 2014)

Workaround
Resize the VxVM volume and file system in separate operations. Use the vxassist command to
increase or decrease the VxVM volume size (or the vxresize command without the –F option).
Use the extendfs or fsadm command to resize the file system.
Renaming VxVM volumes with EVFS enabled makes the volume unusable
The vxedit rename command renames a VxVM volume. The vxedit rename command has
no knowledge of EVFS, so if you have a VxVM volume with EVFS enabled and then rename the
volume, the mapping between the VxVM volume becomes unusable. EVFS commands fail.
Symptoms
The vxedit rename command will complete, but subsequent EVFS operations fail.
Workaround
Disable EVFS and unmap the EVFS volume before renaming the underlying VxVM volume. After
you rename the VxVM volume, you must map the new VxVM volume name to EVFS and enable
the new EVFS volume.
System panics with EVFS file level encryption on VxFS
Defect Number: QXCR1001272570
Symptom:
System panics with EVFS file level encryption on VxFS.
Solution:
Install patch PHKL_43600 to fix this issue.
Non-root users cannot perform administrative task on EVFS volume
Defect number: QXCR1001200068
Symptom:
evfsvol command cannot be executed as non-root user.
Workaround:
Run evfsvol command as root.
12 EVFS