Encrypted Volume and File System v2.0 Release Notes

• 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.
1.5 Enhancements
HP-UX EVFS v2.0 provides the following enhancements:
• CR number: QXCR1000934023
Supports LVM and VxVM volumes greater than 2 TB.
For the LVM and VxVM products, refer to their respective release notes for more information
on the required patches to support volumes greater than 2 TB:
http://www.docs.hp.com/
• CR number: QXCR1000943296
Validates the EVFS entry in the /etc/inittab file during swverify.
• CR number: QXCR1000938048
Supports EVFS volumes that do not have a file system on ServiceGuard. A new EVFS attribute
evfs_raw_vol has been added and ServiceGuard version A.11.18 or above is required.
1.6 Defects Fixed
HP-UX EVFS v2.0 provides the following fixes:
• Defect number: QXCR1000940811
Resolves a system panic when the EMD (EVFS Encrypted Meta Data) located at the beginning
of the EVFS volume is corrupted.
• Defect number: QXCR1000947450
Revolves a data corruption issue with in-line encryption of an EVFS volume that is more
than 4GB in size.
1.7 Known Problems
HP-UX EVFS v2.0 includes the following known problems:
• “Creation of VxFS Filesystem Using mkfs on the EVFS (VxVM) Volume Failed.” (page 12)
• “Creation of HFS Filesystem Exhibits an Unexpected Behavior” (page 12)
• “Failure to Read the Files System Super Block from the Physical Device (LVM/VxVM) when
it is Mapped to EVFS” (page 12)
• “vxresize -F Can Cause Data Loss or Corruption” (page 13)
• “Renaming VxVM Volumes with EVFS Enabled Makes the Volume Unusable” (page 13)
1.5 Enhancements 11