Veritas Storage Foundation and High Availability Solutions Release Notes

126About Veritas Storage Foundation and High Availability SolutionsKnown issuesTo resolve this issue1 Note the TargetID and LunID on which the svsiscsiadm create luncommand failed. To find the failed LunID, note the last LunID for the targeton which svsiscsiadm create lun command failed with the use of thesvsiscsiadm list command. To calculate the failed LunID, add 1 to lastLunID seen by the svsiscsiadm list command.2 Go to the configuration directory for the TargetID:# cd /etc/iscsi/TargetID .3 Delete the symlink pointing to path of LUN backing file which failed to getadded. The below LunID is the failed LunID, which is a result of calculationin point 1:# rm -f /etc/iscsi/TargetID/lun.($lunid + 1)After removal of the symlink you should be able to add LUNs on the unusabletarget.VirtualStore machine clones created while the VirtualStore cluster rebootswill probably not start (2164664)In some cases when you clone while rebooting the SVS nodes, you may receiveseveral of the following error messages:clone vms could not start X serverWorkaroundDelete all the clones that got created while the node crashed and redo the cloningoperation.Cloning may not work (2348628)If you cannot clone and you are using the VMware vAPP and OVF templates, thenyou must disable the vApp.WorkaroundTo disable the vAPP1 In VI Client, right-click on the virtual machine > Edit Settings > Options >vApp Options.2 Click Disable.