Encrypted Volume and File System v2.0 Release Notes

• Process management cumulative patch: PHKL_38650
• Process-specific Data cumulative patch: PHKL_38800
• The fs_spec cumulative patch: PHKL_38936
• The fs_util cumulative patch: PHKL_38937
You can download patches from the HP IT Resource Center at:
http://www2.itrc.hp.com/service/patch/mainPage.do
1.4 Limitations
The EVFS product has the following limitations:
• EVFS operates with LVM, VxVM and physical volumes only. Each EVFS volume is mapped
to an underlying LVM, VxVM or physical volume.
• You can use an alternate link to specify an LVM or VxVM volume or an alternate device
path to specify a whole disk for the evfsadm map command. However, when creating
EVFS volumes, do not:
— Create multiple EVFS volumes that reference the same LVM or VxVM volume
— Create multiple EVFS volumes that reference the same physical disk when using whole
disk access
— Specify different multipaths to the same physical disk when using whole disk access
— Specify persistent and legacy device files that point to the same physical disk
CAUTION: If you create multiple EVFS volumes that reference the same LVM or VxVM
volume or the same whole disk device, data corruption can occur.
• You enable EVFS encryption and decryption for an EVFS volume as a single unit. When
you enable EVFS encryption and decryption for a volume, EVFS encrypts and decrypts the
data blocks as the blocks are accessed, and all read operations through the EVFS volume
receive decrypted data as output, and users can access individual files in cleartext. You must
use normal HP-UX file system permissions and access control to restrict access to the data.
• You cannot encrypt the following objects:
— Files or disk areas used during system boot. This includes the following objects:
◦ the root file system (/)
◦ the HP-UX kernel directory (/stand)
◦ the /usr directory
1.4 Limitations 9