Encrypted Volume and File System v1.1.2 Release Notes

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 v1.1.2 includes the following known problems:
“Possible Device File Collision” (page 11)
“vxresize -F Can Cause Data Loss or Corruption” (page 11)
“Renaming VxVM Volumes with EVFS Enabled Makes the Volume Unusable” (page 12)
1.7.1 Possible Device File Collision
(SR 8606459127) Executing the newfs or mkfs command for an EVFS volume can fail on systems
with components that call alloc_fake_device(), such as systems that are NFS clients. This
problem is caused by a defect in the alloc_fake_device() routine.
Symptoms
The newfs or mkfs command fails with a message similar to the following:
vxfs mkfs: /dev/evfs/vg01/relvol1 is mounted, cannot mkfs
The output from the lsdev command shows that the character major number used by the device
driver fake is the same as the block major number used by the device driver evfsevol. In the
example that follows, the common number is 2:
# lsdev
Character Block Driver Class
:
:
2 -1 fake pseudo
:
:
115 2 evfsevol pseudo
Workaround
The following workaround is only necessary and applicable to HP-UX 11i v2 Update 2.
Install patch PHKL_37146. You can download patches from the HP IT Resource Center at:
http://www2.itrc.hp.com/service/patch/mainPage.do.
1.7.2 vxresize -F Can Cause Data Loss or Corruption
The vxresize F command resizes a VxVM volume and the file system mounted on the
volume. The vxresize command has no knowledge of EVFS, so if you configure EVFS on a
VxVM volume and then execute the vxresize F command, vxresize does not allocate space
for the EVFS data structure (the EMD) on the volume. The vxresize -F command completes,
but file operations might fail; data might be lost or corrupted.
Symptoms
The vxresize -F command completes, but file operations might fail; data might be lost or
corrupted.
1.7 Known Problems 11