Encrypted Volume and File System v2.2 Release Notes (777845-001, April 2014)
• The evfsadm trace command is intended for use by support personnel only. HP does not
support this feature on customer environments.
• During inline encryption, the volume is not accessible until the entire operation is completed.
• The Multi Volume File System feature of Veritas, which is not supported by EVFS.
• EVFS is currently available in English only.
• Secure Sessions limit: 16K secure sessions per system.
• Volume limit: 1023 encrypted volumes per system.
• ServiceGuard version A.11.18 or later using modular packages supports EVFS volumes without
a file system.
• On an EFS volume, the file size is limited to a maximum file size minus the size of the EMD
(4k).
• EVFS is not supported with ServiceGuard/SGeRAC shared activation.
• The following features on ServiceGuard version A.11.19 are not supported by EVFS:
Online package configuration◦
◦ Partial-startup maintenance mode
• Writing to a EVFS device that is not mapped by EVFS (for example, when EVFS is not running),
can cause data corruption. The maximum user name, group name, or key name length
supported by EVFS is 100.
• Because of the computing intensive nature of the encryption algorithms, HP recommends at
least one additional CPU when using EVFS software.
Defects fixed
There are no defect fixes in this release.
Known Problems
HP-UX EVFS v2.1 includes the following known problems:
• “Creation of VxFS Filesystem using mkfs on the EVFS (VxVM) volume failed” (page 10).
• “Creation of HFS Filesystem exhibits an unexpected behavior” (page 11).
• “Failure to read the Files System super block from the physical device (LVM/VxVM) when it
is mapped to EVFS” (page 11).
• “vxresize -F can cause data loss or corruption” (page 11).
• “Renaming VxVM volumes with EVFS enabled makes the volume unusable” (page 12).
• “System panics with EVFS file level encryption on VxFS” (page 12).
• “Non-root users cannot perform administrative task on EVFS volume” (page 12).
Creation of VxFS Filesystem using mkfs on the EVFS (VxVM) volume failed
Defect number: QXCR1000900650
Symptom
Using the mkfs command to create a VxFS file system on a VxVM volume configured for EVS
mode does not work.
Solution
Install patch PHCO_39474 to get the new mkfs binary.
10 EVFS