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

Workaround
If you cannot install patch PHCO_39474, use the newfs command instead of the mkfs command
to create a VxFS file system.
Creation of HFS Filesystem exhibits an unexpected behavior
Defect number: QXCR1000900954
Symptom
You can successfully create an HFS file system on a physical device or volume (for example,
/dev/vg01/lvol1) using the mkfs or newfs command, even though the corresponding EVFS
device (/dev/evfs/vg01/lvol1) is already mounted. Similarly, you can successfully create an
HFS file system on a EVFS device using the mkfs or newfs command, even though the
corresponding physical device or volume is already mounted.
WARNING! Do not try to create an HFS file system using a physical volume if the corresponding
EVFS volume is already mounted. Similarly, do not try to create an HFS file system using an EVFS
volume if the corresponding physical volume is already mounted. This may result in file system
corruption that would make the data unrecoverable.
Workaround
There is no work around for this issue.
Failure to read the Files System super block from the physical device (LVM/VxVM)
when it is mapped to EVFS
The fsadm command fails to read the files system super block from the physical device (LVM/VxVM)
when it is mapped to EVFS.
Symptom:
When extending the file system, the following error is displayed:
vxfs fsadm: V-3-20285: filesystem /mnt/evfsmnt does not match filesystem super-block on /dev/vg01/evfs_lvol1
vxfs fsadm: V-3-20284: use [-r] to specify a raw device
Workaround
To work around this issue, do one of the following workarounds:
• Mount the file system on the EVFS volume instead of on the physical volume and use the fsadm
command on EVFS volume to increase the file system size.
• Unmap the EVFS volume configured for EVS mode and run fsadm on physical volume.
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.
Known Problems 11