Veritas Storage Foundation Release Notes
Veritas Storage Foundation⢠Release Notes: HP-UX - Symantec
Veritas Storage Foundation⢠Release Notes: HP-UX - Symantec
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
54<br />
<strong>Storage</strong> <strong>Foundation</strong> <strong>Release</strong> <strong>Notes</strong><br />
Known issues<br />
%dirty may lag from actual percentage dirty for instant snap data cache object<br />
(DCO) volumes. That is, the command output may show less %dirty than actual.<br />
Encapsulation of a multi-pathed root disk fails if the dmpnode<br />
name and any of its path names are not the same (2607706)<br />
The encapsulation of a multi-pathed root disk fails if the dmpnode name and any<br />
of its path name are not the same.<br />
For example:<br />
Dmpnode:sdh<br />
Paths: sda sdb<br />
Work-around:<br />
Before running the encapsulation command (vxencap), run the following command:<br />
# vxddladm assign names<br />
Recovery and rollback to original configuration may not<br />
succeed if the system reboots while the online migration setup<br />
is in partial state (2611423)<br />
During online migration from LVM to VxVM volumes, if there is a system reboot<br />
when the migration setup is in partial state, that is, the start operation has not<br />
completed successfully, then the recover and abort operations might not be able<br />
to recover and rollback the configuration.<br />
Workaround: This needs manual intervention for cleanup, depending on the state,<br />
to restore the original configuration.<br />
During online migration from LVM to VxVM volumes, LVM<br />
sometimes incorrectly reports the remapped LVM device paths<br />
as valid LVM volumes<br />
Problem: In a migrated or committed configuration, only the renamed LVM names<br />
of the form _vxlv are valid LVM volumes. The original LVM names,<br />
in turn, point to target VxVM volumes. However, LVM sometimes incorrectly<br />
reports these original LVM device paths pointing to VxVM volumes, as valid LVM<br />
volumes.<br />
Do not assume these as LVM volumes or do any operations on them, as it would<br />
disrupt the application’s access to the target VxVM volumes.