Veritas Storage Foundation and High Availability Solutions Release Notes
Veritas Storage Foundation⢠and High ... - SORT - Symantec
Veritas Storage Foundation⢠and High ... - SORT - Symantec
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
60About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Known issuesvxmirror to SAN destination failing when 5 partition layout is present: forexample, root, swap, home, var, usr (2815311)The vxmirror comm<strong>and</strong> may fail with following error on a Solaris 10 host, for athin LUN, if more than one partition excluding root <strong>and</strong> swap is present.VxVM vxbootsetup WARNING V-5-2-5667 Max volume count 5 exceeded.Example:# /etc/vx/bin/vxmirror" -f -g rootdg_17_23_49 rootdisk01 \rootdisk02! vxassist -g rootdg_17_23_49 mirror swapvol rootdisk02! vxassist -g rootdg_17_23_49 mirror rootvol rootdisk02! vxassist -g rootdg_17_23_49 mirror usr rootdisk02! vxassist -g rootdg_17_23_49 mirror var rootdisk02! vxassist -g rootdg_17_23_49 mirror home rootdisk02! vxbootsetup -g rootdg_17_23_49VxVM vxbootsetup WARNING V-5-2-5667 Max volume count 5 exceeded.VxVM vxbootsetup ERROR V-5-2-5678 Skipping volume 'home_dcl'because no free partitions are available on disk 'disk_0'.Either remove the volume or make a partition availableVxVM vxbootsetup WARNING V-5-2-5667 Max volume count 5 exceeded.VxVM vxbootsetup ERROR V-5-2-5678 Skipping volume 'usr_dcl'because no free partitions are available on disk 'disk_0'.Either remove the volume or make a partition availableVxVM vxbootsetup WARNING V-5-2-5667 Max volume count 5 exceeded.VxVM vxbootsetup ERROR V-5-2-5678 Skipping volume 'var_dcl' becauseno free partitions are available on disk 'disk_0'.Either remove the volume or make a partition available/usr/lib/vxvm/bin/vxmksdpart: 3pardata0_2492: is not an identifierDiskgroup import of BCV luns using -o updateid <strong>and</strong> -o useclonedev optionsis not supported if the diskgroup has mirrored volumes with DCO or hassnapshots. (2831658)VxVM uses guid stored in configuration to uniquely identify all objects. The DCOvolume stores the guid of mirrors <strong>and</strong> snapshots. If the diskgroup is importedwith -o updateid <strong>and</strong> -o useclonedev, it changes the guid of objects in VxVMconfiguration database <strong>and</strong> the guids stored in DCO volume are not updated. Sothe operations involving DCO will not be able to find objects with the stored guid<strong>and</strong> this could lead to failure of certain operations involving DCO or could lead tounexpected behaviour.Workaround:No workaround available.
Change language