VxVM vxdisk ERROR V-5-1-5433 Device systemA00_oracle-fs1-2-0_00076: init failed:
Disk Ioctl failed
This is due to the names of the Oracle FS1-2 luns getting prefixed with the the hostname. With the addition of the disk slice the resulting DA name will become greater than 31 characters. This will in turn result in the slices getting destroyed and the disk initialisation failing.
There are two confirmed workarounds for this initialisation issue:
1. Exclude the libvxoracle_FS1.so asl using the 'vxddladm exclude libname=libvxoracle_FS1.so' command and the disks can be successfully initialised.
2. Change the namingscheme to OSN using the 'vxddladm set namingscheme=osn' command and the disks can be successfully initialised. The namingscheme can then be switched back to EBN using the 'vxddladm set namingscheme=ebn' command.
Veritas has reproduced this issue in-house and has identified root-cause of the issue along with the fix. The fix will be included in the next GA release of the VRTSaslapm package.
The initialisation of Oracle FS1-2 luns is failing on InfoScale 7.2 and VRTSaslapm 7.2.0.100 on rhel6.8.
# vxdisksetup -i systemA00_oracle-fs1-2-0_00076
VxVM vxdisk ERROR V-5-1-5433 Device systemA00_oracle-fs1-2-0_00076: init failed:
Disk Ioctl failed
ETrack: 3917681