README VERSION : 1.1 README CREATION DATE : 2012-09-27 PATCH-ID : PHCO_43065 PATCH NAME : VRTSvxvm 5.1SP1RP2 BASE PACKAGE NAME : VRTSvxvm BASE PACKAGE VERSION : 5.1.100.000/5.1.100.001 SUPERSEDED PATCHES : PHCO_42992 REQUIRED PATCHES : PHKL_43064 INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : hpux1131 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : CORE , CORRUPTION , HANG , MEMORYLEAK , PANIC , PERFORMANCE PATCH CRITICALITY : CRITICAL HAS KERNEL COMPONENT : NO ID : NONE REBOOT REQUIRED : YES PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer to the install/upgrade/rollback section in the Release Notes PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to the install/upgrade/rollback section in the Release Notes SPECIAL INSTRUCTIONS: --------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- 2070079 (1903700) Removing mirror using vxassist does not work. 2205574 (1291519) After multiple VVR migrate operations, vrstat fails to output statistics. 2427560 (2425259) vxdg join operation fails with VE_DDL_PROPERTY: Property not found in the list 2442751 (2104887) vxdg import error message needs improvement for cloned diskgroup import failure. 2442827 (2149922) Record the diskgroup import and deport events in syslog 2485261 (2354046) man page for dgcfgrestore is incorrect. 2492568 (2441937) vxconfigrestore precommit fails with awk errors 2495590 (2492451) vxvm-startup2 launches vxesd without checking install-db. 2513457 (2495351) VxVMconvert utility was incompatible to migrate data across platforms from native LVM configurations. 2515137 (2513101) User data corrupted with disk label information 2560539 (2252680) vxtask abort does not cleanup tasks properly. 2567623 (2567618) VRTSexplorer coredumps in checkhbaapi/print_target_map_entry. 2576605 (2576602) 'vxdg listtag' should give error message and display correct usage when executed with wrong syntax 2626742 (2626741) Using vxassist -o ordered and mediatype:hdd options together do not work as expected 2626745 (2626199) "vxdmpadm list dmpnode" printing incorrect path-type 2627000 (2578336) Failed to online the cdsdisk. 2627004 (2413763) Uninitialized memory read results in a vxconfigd coredump 2641932 (2348199) vxconfig dumps core while importing a Disk Group 2646417 (2556781) In cluster environment, import attempt of imported disk group may return wrong error. 2652161 (2647975) Customer ran hastop -local and shared dg had splitbrain 2677025 (2677016) Veritas Event Manager(vxesd(1M)) daemon dumps core when main thread tries to close one of its thread (which hold connection with HP Event Manager). 2690959 (2688308) When re-import of disk group fails during master takeover, other shared disk groups should not be disabled. 2695231 (2689845) Data disk can go in error state when data at the end of the first sector of the disk is same as MBR signature 2705101 (2216951) vxconfigd dumps core because chosen_rlist_delete() hits NULL pointer in linked list of clone disks 2706024 (2664825) DiskGroup import fails when disk contains no valid UDID tag on config copy and config copy is disabled. 2706038 (2516584) startup scripts use 'quit' instead of 'exit', causing empty directories in /tmp 2737373 (2556467) DMP-ASM: disabling all paths and reboot of the host causes losing of /etc/vx/.vxdmprawdev records 2747340 (2739709) Disk group rebuild fails as the links between volume and vset were missing from 'vxprint -D -' output. 2759895 (2753954) When a cable is disconnected from one port of a dual-port FC HBA, the paths via another port are marked as SUSPECT PATH. 2763211 (2763206) "vxdisk rm" command dumps core when disk name of very large length is given 2768492 (2277558) vxassist outputs a misleading error message during snapshot related operations. 2802370 (2585239) VxVM commands run very slow on setup with tape devices 2804911 (2637217) Document new storage allocation attribute support in vradmin man page for resizevol/resizesrl. 2821143 (1431223) "vradmin syncvol" and "vradmin syncrvg" commands do not work if the remote diskgroup and vset names are specified when synchronizing vsets. 2821452 (2495332) vxcdsconvert fails if the private region of the disk to be converted is less than 1 MB. 2821515 (2617277) Man pages for the vxautoanalysis and vxautoconvert commands are missing from the base package. 2821537 (2792748) Node join fails because of closing of wrong file descriptor 2821678 (2389554) vxdg listssbinfo output is incorrect. 2826129 (2826125) VxVM script daemon is terminated abnormally on its invocation. 2826607 (1675482) "vxdg list " command shows configuration copy in new failed state. 2827939 (2088426) Re-onlining of disks in DG during DG deport/destroy. 2836910 (2818840) Enhance the vxdmpasm utility to support various permissions and "root:non- system" ownership can be set persistently. 2852270 (2715129) Vxconfigd hangs during Master takeover in a CVM (Clustered Volume Manager) environment. 2858859 (2858853) After master switch, vxconfigd dumps core on old master. 2859390 (2000585) vxrecover doesn't start remaining volumes if one of the volumes is removed during vxrecover command run. 2860449 (2836798) In VxVM, resizing simple EFI disk fails and causes system panic/hang. 2860451 (2815517) vxdg adddisk allows mixing of clone & non-clone disks in a DiskGroup. 2882488 (2754819) Diskgroup rebuild through 'vxmake -d' loops infinitely if the diskgroup configuration has multiple objects on a single cache object. 2886083 (2257850) vxdiskadm leaks memory while performing operations related to enclosures. 2911009 (2535716) VxVMconvert doesn't support migration of data for large number of LVM/VG configuration since it always creates private region at static offsets - 128th block 2911010 (2627056) 'vxmake -g DGNAME -d desc-file' fails with very large configuration due to memory leaks SUMMARY OF KNOWN ISSUES: ----------------------------------------- 2223250(2165829) Node is not able to join the cluster when recovery is in progress. 2900968(2920800) Creation of VxVM BOOT fails with legacy device tree removed. 2922551(2826905) vxautoconvert(1M) fails to covert an LVM VG to a VxVM DG with new namingscheme. 2937442(2942692) On HPIVM 6.1, VxVM can not identify "thin disks" KNOWN ISSUES : -------------- * INCIDENT NO::2223250 TRACKING ID ::2165829 SYMPTOM:: Node join fails if the recovery for the leaving node is not completed. WORKAROUND:: Retry node join after the recovery is completed. * INCIDENT NO::2900968 TRACKING ID ::2920800 SYMPTOM:: If OS legacy device special files are not available, following VXVM operation may fail: Creating VXVM BOOT disk by running vxdisksetup -B WORKAROUND:: There is no known * INCIDENT NO::2922551 TRACKING ID ::2826905 SYMPTOM:: vxautoconvert(1M) fails to covert an LVM VG to a VxVM DG with new namingscheme. Convert fails and not able to roll back LVM VG's original state. WORKAROUND:: Change to different naming scheme before convert procedure using vxautoconvert(1M) and once the conversion is finished, return back to the original(new namingscheme). * INCIDENT NO::2937442 TRACKING ID ::2942692 SYMPTOM:: On HPIVM 6.1, VxVM can not identify "thin disks". When "vxdisk -o thin list" command is run, the follwing error message is displayed: "VxVM vxdisk INFO V-5-1-14413 No Thin Provisioned disk are attached to the system." WORKAROUND:: None FIXED INCIDENTS: ---------------- PATCH ID:PHCO_43065 * INCIDENT NO:2070079 TRACKING ID:1903700 SYMPTOM: vxassist remove mirror does not work if nmirror and alloc is specified, giving an error "Cannot remove enough mirrors" DESCRIPTION: During remove mirror operation, VxVM does not perform correct analysis of plexes. Hence the issue. RESOLUTION: Necessary code changes have been done so that vxassist works properly. * INCIDENT NO:2205574 TRACKING ID:1291519 SYMPTOM: After two VVR migrate operations, vrstat command does not output any statistics. DESCRIPTION: Migrate operation results in RDS (Replicated Data Set) information getting updated on both primary and secondary side vradmind. After multiple migrate operations, stale handle to older RDS is used by vrstat to retrieve statistics resulting in the failure. RESOLUTION: Necessary code changes have being made to ensure correct and updated RDS handle is used by vrstat to retrieve statistics. * INCIDENT NO:2427560 TRACKING ID:2425259 SYMPTOM: vxdg join operation fails throwing error "join failed : Invalid attribute specification". DESCRIPTION: For the disk name containing "/" character e. g. cciss/c0d1, join operation fails to parse the name of disks and hence returns with error. RESOLUTION: Code changes are made to handle special characters in disk name. * INCIDENT NO:2442751 TRACKING ID:2104887 SYMPTOM: vxdg import fails with following ERROR message for cloned device import, when original diskgroup is already imported with same DGID. # vxdg -Cfn clonedg -o useclonedev=on -o tag=tag1 import testdg VxVM vxdg ERROR V-5-1-10978 Disk group testdg: import failed: Disk group exists and is imported DESCRIPTION: In case of clone device import, vxdg import without "-o updateid" option fails, if original DG is already imported. The error message returned may be interpreted as diskgroup with same name is imported, while actually the dgid is duplicated and not the dgname. RESOLUTION: vxdg utility is modified to return better error message for cloned DG import. It directs you to get details from system log. Details of conflicting dgid and suggestion to use "-o updateid" are added in the system log. * INCIDENT NO:2442827 TRACKING ID:2149922 SYMPTOM: Record the diskgroup import and deport events in the /var/adm/syslog/syslog.log file. Following type of message can be logged in syslog: vxvm:vxconfigd: V-5-1-16254 Disk group import of succeeded. DESCRIPTION: With the diskgroup import or deport, appropriate success message or failure message with the cause for failure should be logged. RESOLUTION: Code changes are made to log diskgroup import and deport events in syslog. * INCIDENT NO:2485261 TRACKING ID:2354046 SYMPTOM: dgcfgrestore man page examples are incorrect. DESCRIPTION: Example 1: Restore the VxVM configuration information for the VxVM disk disk01 on the replacement disk device c0t7d0 that was part of the single-disk disk group onediskdg using the default configuration file /etc/vxvmconf/dg00.conf: ## Restore configuration data # dgcfgrestore -n onediskdg c0t7d0 The last step of this example will not work. If we create disk group with same name then the default configuration file /etc/vxvmconf/.conf is moved to etc/vxvmconf/.conf.old and new configuration is written to default configuration file. The -n option will read configuration from default configuration file and dgcfgrestore will fail. Example 2: The final example restores the VxVM configuration information for the VxVM disk, disk01 for failed disk device c0t2d0, which was part of a single-disk disk group, foodg, to disk, c0t3d0. The default configuration file, /etc/vxvmconf/foodg.conf is used. # Initialize c0t3d0 for use by VxVM /etc/vx/bin/vxdisketup -i c0t3d0 # Create disk group using this disk vxdg init onediskdg disk01=c0t3d0 # Restore configuration data dgcfgrestore -n foodg -o c0t3d0 c0t2d0 In this example to restore configuration of foodg on replacement disk we need to create new disk group with same name i.e. foodg. " -o" option refers to old disk media name. In the last step -o option is used with new disk media name so dgcfgrestore will fail. RESOLUTION: This document defect is addressed by document change. For Example 1, -f option is used to read disk group configuration from /etc/vxvmconf/.conf.old file. For Example 2, new disk group name is changed to foodg and -o option is used with old disk media name. * INCIDENT NO:2492568 TRACKING ID:2441937 SYMPTOM: vxconfigrestore(1M) command fails with the following error... "The source line number is 1. awk: Input line 22 | cannot be longer than 3,000 bytes." DESCRIPTION: In the function where we read the disk attributes from backup, we are getting the disk attributes in the variable "$disk_attr". The value of this variable "$disk_attr" comes out to be a line longer than 3000 bytes. Later this variable "$disk_attr" is used by awk(1) command to parse it and hits the awk(1) limitation of 3000 bytes. RESOLUTION: The code is modified to replace awk(1) command with cut(1) command which does not have this limitation. * INCIDENT NO:2495590 TRACKING ID:2492451 SYMPTOM: If the Veritas Volume Manager (VxVM) is not configured, the following messages are observed in syslog file: vxesd[1554]: Event Source daemon started vxesd[1554]: HBA API Library Loaded vxesd[1554]: Registration with DMP failed DESCRIPTION: The presence of "/etc/vx/reconfig.d/state.d/install-db" file indicates that VxVM is not configured. The startup script "/sbin/init.d/vxvm-startup2" does not check the presence of install-db file and starts the vxesd(1M) daemon. RESOLUTION: The code has been modified to check the presence of install-db file and start vxesd(1M) daemon accordingly. * INCIDENT NO:2513457 TRACKING ID:2495351 SYMPTOM: VxVMconvert utility was incompatible to migrate data across platforms from native LVM configurations. DESCRIPTION: VxVMconvert used for migration of customer data did not take into consideration varied LVM configuration scenarios that hindered its ability to do successful conversion. For example, HPUX Volume Group with large number of Logical and Physical Volumes requires significant metadata size to be stored on the disk for successful conversion. However VxVMconvert failed to calculate metadata size based on the configuration rather created static and lesser sizes thereby leading to failure in migration of data. RESOLUTION: Enhanced VxVMconvert utility to handle different LVM configuration scenarios to migrate data across platforms. * INCIDENT NO:2515137 TRACKING ID:2513101 SYMPTOM: When VxVM is upgraded from 4.1MP4RP2 to 5.1SP1RP1, the data on CDS disk gets corrupted. DESCRIPTION: When CDS disks are initialized with VxVM version 4.1MP4RP2, the number of cylinders are calculated based on the disk raw geometry. If the calculated number of cylinders exceed Solaris VTOC limit (65535), because of unsigned integer overflow, truncated value of number of cylinders gets written in CDS label. After the VxVM is upgraded to 5.1SP1RP1, CDS label gets wrongly written in the public region leading to the data corruption. RESOLUTION: The code changes are made to suitably adjust the number of tracks & heads so that the calculated number of cylinders be within Solaris VTOC limit. * INCIDENT NO:2560539 TRACKING ID:2252680 SYMPTOM: When a paused VxVM (Veritas Volume Manager task) is aborted using 'vxtask abort' command, it does not get aborted appropriately. It continues to show up in the output of 'vxtask list' command and the corresponding process does not get killed. DESCRIPTION: As appropriate signal is not sent to the paused VxVM task which is being aborted, it fails to abort and continues to show up in the output of 'vxtask list' command. Also, its corresponding process does not get killed. RESOLUTION: Code changes are done to send an appropriate signal to paused tasks to abort them. * INCIDENT NO:2567623 TRACKING ID:2567618 SYMPTOM: VRTSexplorer coredumps in checkhbaapi/print_target_map_entry which looks like: print_target_map_entry() check_hbaapi() main() _start() DESCRIPTION: checkhbaapi utility uses HBA_GetFcpTargetMapping() API which returns the current set of mappings between operating system and fibre channel protocol (FCP) devices for a given HBA port. The maximum limit for mappings was set to 512 and only that much memory was allocated. When the number of mappings returned was greater than 512, the function that prints this information used to try to access the entries beyond that limit, which resulted in core dumps. RESOLUTION: The code has been changed to allocate enough memory for all the mappings returned by HBA_GetFcpTargetMapping(). * INCIDENT NO:2576605 TRACKING ID:2576602 SYMPTOM: listtag option for vxdg command gives results even when executed with wrong syntax. DESCRIPTION: The correct syntax, as per vxdg help, is "vxdg listtag [diskgroup ...]". However, when executed with the wrong syntax, "vxdg [-g diskgroup] listtag", it still give results. RESOLUTION: Please use the correct syntax as per help for vxdg command. The command has being modified from 6.0 release onwards to display error and usage message when wrong syntax is used. * INCIDENT NO:2626742 TRACKING ID:2626741 SYMPTOM: Vxassist when used with "-o ordered " and "mediatype:hdd" during striped volume make operation does not maintain disk order. DESCRIPTION: Vxassist when invoked with "-o ordered" and "mediatype:hdd" options while creating a striped volume, does not maintain the disk order provided by the user. First stripe of the volume should correspond to the first disk provided by the user. RESOLUTION: Rectified code to use the disks as per the user specified disk order. * INCIDENT NO:2626745 TRACKING ID:2626199 SYMPTOM: "vxdmpadm list dmpnode" command shows the path-type value as "primary/secondary" for a LUN in an Active-Active array as below when it is suppose to be NULL value. dmpdev = c6t0d3 state = enabled ... array-type = A/A ###path = name state type transport ctlr hwpath aportID aportWWN attr path = c23t0d3 enabled(a) secondary FC c30 2/0/0/2/0/0/0.0x50060e800 5c0bb00 - - - DESCRIPTION: For a LUN under Active-Active array the path-type value is supposed to be NULL. In this specific case other commands like "vxdmpadm getsubpaths dmpnode=<>" were showing correct (NULL) value for path-type. RESOLUTION: The "vxdmpadm list dmpnode" code path failed to initialize the path-type variable and by default set path-type to "primary or secondary" even for Active-Active array LUN's. This is fixed by initializing the path-type variable to NULL. * INCIDENT NO:2627000 TRACKING ID:2578336 SYMPTOM: I/O error is encountered while accessing the cdsdisk. DESCRIPTION: This issue is seen only on defective cdsdisks, where s2 partition size in sector 0 label is less than sum of public region offset and public region length. RESOLUTION: A solution has been implemented to rectify defective cdsdisk at the time the cdsdisk is onlined. * INCIDENT NO:2627004 TRACKING ID:2413763 SYMPTOM: vxconfigd, the VxVM daemon dumps core with the following stack: ddl_fill_dmp_info ddl_init_dmp_tree ddl_fetch_dmp_tree ddl_find_devices_in_system find_devices_in_system mode_set setup_mode startup main __libc_start_main _start DESCRIPTION: Dynamic Multi Pathing node buffer declared in the Device Discovery Layer was not initialized. Since the node buffer is local to the function, an explicit initialization is required before copying another buffer into it. RESOLUTION: The node buffer is appropriately initialized using memset() to address the coredump. * INCIDENT NO:2641932 TRACKING ID:2348199 SYMPTOM: vxconfigd dumps core during Disk Group import with the following function call stack strcmp+0x60 () da_find_diskid+0x300 () dm_get_da+0x250 () ssb_check_disks+0x8c0 () dg_import_start+0x4e50 () dg_reimport+0x6c0 () dg_recover_all+0x710 () mode_set+0x1770 () setup_mode+0x50 () startup+0xca0 () main+0x3ca0 () DESCRIPTION: During Disk Group import, vxconfigd performs certain validations on the disks. During one such validation, it iterates through the list of available disk access records to find a match with a given disk media record. It does a string comparison of the disk IDs in the two records to find a match. Under certain conditions, the disk ID for a disk access record may have a NULL value. vxconfigd dumps core when it passes this to strcmp() function. RESOLUTION: Code was modified to check for disk access records with NULL value and skip them from disk ID comparison. * INCIDENT NO:2646417 TRACKING ID:2556781 SYMPTOM: In cluster environment, importing a disk group which is imported on another node will result in wrong error messages like given below: VxVM vxdg ERROR V-5-1-10978 Disk group : import failed: Disk is in use by another host DESCRIPTION: When VxVM is translating a given disk group name to disk group id during the disk group import process, an error return indicating that the disk group is in use by another host may be overwritten by a wrong error. RESOLUTION: The source code has been changed to handle the return value in a correct way. * INCIDENT NO:2652161 TRACKING ID:2647975 SYMPTOM: Serial Split Brain (SSB) condition caused Cluster Volume Manager(CVM) Master Takeover to fail. The below vxconfigd debug output was noticed when the issue was noticed: VxVM vxconfigd NOTICE V-5-1-7899 CVM_VOLD_CHANGE command received V-5-1-0 Preempting CM NID 1 VxVM vxconfigd NOTICE V-5-1-9576 Split Brain. da id is 0.5, while dm id is 0.4 for dm cvmdgA-01 VxVM vxconfigd WARNING V-5-1-8060 master: could not delete shared disk groups VxVM vxconfigd ERROR V-5-1-7934 Disk group cvmdgA: Disabled by errors VxVM vxconfigd ERROR V-5-1-7934 Disk group cvmdgB: Disabled by errors ... VxVM vxconfigd ERROR V-5-1-11467 kernel_fail_join() : Reconfiguration interrupted: Reason is transition to role failed (12, 1) VxVM vxconfigd NOTICE V-5-1-7901 CVM_VOLD_STOP command received DESCRIPTION: When Serial Split Brain (SSB) condition is detected by the new CVM master, on Veritas Volume Manager (VxVM) versions 5.0 and 5.1, the default CVM behaviour will cause the new CVM master to leave the cluster and causes cluster-wide downtime. RESOLUTION: Necessary code changes have been done to ensure that when SSB is detected in a diskgroup, CVM will only disable that particular diskgroup and keep the other diskgroups imported during the CVM Master Takeover, the new CVM master will not leave the cluster with the fix applied. * INCIDENT NO:2677025 TRACKING ID:2677016 SYMPTOM: Veritas Event Manager(vxesd(1M)) daemon dumps core when main thread tries to close one of its thread (which hold connection with HP Event Manager). The stack trace of main thread will be as follows: _evmmiscFree+0 () from /usr/lib/hpux32/libevm.so EvmConnDestroy+0x150 () from /usr/lib/hpux32/libevm.so volhp_evm_stop+0x30 () register_evm_events+0x60 () DESCRIPTION: When main thread of vxesd encounters an error in processing client requests, it starts closing others threads. But when it starts closing EVM thread, main thread destroys the connection used by EVM thread and if there is a context switch at this point to EVM thread, there is a chance of vxesd dumping core. RESOLUTION: Code changes have been done to ensure that EVM thread destroy its connection rather than main thread doing it. * INCIDENT NO:2690959 TRACKING ID:2688308 SYMPTOM: When re-import of a disk group fails during master takeover, it makes all the shared disk groups to be disabled. It also results in the corresponding node (new master) leaving the cluster. DESCRIPTION: In cluster volume manager when master goes down, the upcoming master tries to re-import the disk group. If some error occurs while re-importing the disk group then it disables all the shared disk groups and the new master leaves the cluster. This may result in cluster outage. RESOLUTION: Code changes are made to disable the disk group on which error occurred while re-importing and continue import of the other shared disk groups. * INCIDENT NO:2695231 TRACKING ID:2689845 SYMPTOM: Disks are seen in error state. hitachi_usp-vm0_11 auto - - error DESCRIPTION: When data at the end of the first sector of the disk is same as MBR signature, Volume Manager misinterprets the data disk as MBR disk. Accordingly, partitions are determined but format determination fails for these fake partitions and disk goes into error state. RESOLUTION: Code changes are made to check the status field of the disk along with the MBR signature. Valid status fields for MBR disk are 0x00 and 0x80. * INCIDENT NO:2705101 TRACKING ID:2216951 SYMPTOM: The vxconfigd daemon core dumps in the chosen_rlist_delete() function and the following stack trace is displayed: chosen_rlist_delete() req_dg_import_disk_names() request_loop() main() DESCRIPTION: The vxconfigd daemon core dumps when it accesses a NULL pointer in the chosen_rlist_delete() function. RESOLUTION: The code is modified to handle the NULL pointer in the chosen_rlist_delete() function * INCIDENT NO:2706024 TRACKING ID:2664825 SYMPTOM: The following two issues are seen when a cloned disk group having a mixture of disks which are clones of disks initialized under VxVM version 4.x and 5.x is imported. (i) The following error will be seen without "-o useclonedev=on -o updateid" options on 5.x environment with the import failure. # vxdg -Cf import VxVM vxdg ERROR Disk group : import failed: Disk group has no valid configuration copies (ii) The following warning will be seen with "-o useclonedev=on -o updateid" options on 5.x environment with the import success. # vxdg -Cf -o useclonedev=on -o updateid import VxVM vxdg WARNING Disk : Not found, last known location: ... DESCRIPTION: The vxconfigd, a VxVM daemon, imports a disk group having disks where all the disks should be either cloned or standard(non-clone). If the disk group has a mixture of cloned and standard devices, and user attempts to import the disk group - (i) without "-o useclonedev=on" options, only standard disks are considered for import. The import would fail if none of the standard disks have a valid configuration copy. (ii) with "-o useclonedev=on" option, the import would succeed, but the standard disks go missing because only clone disks are considered for import. A disk which is initialized in the VxVM version earlier to 5.x has no concept of Unique Disk Identifier(UDID) which helps to identify the cloned disk. It could not be flagged as cloned disk even if it is indeed a cloned disk. This results in the issues (i) and (ii). RESOLUTION: The source code is modified to set the appropriate flags so that the disks initialized in VxVM 4.X will be recognized as "cloned", and both of the issues (i) and (ii) will be avoided. * INCIDENT NO:2706038 TRACKING ID:2516584 SYMPTOM: There are many random directories not cleaned up in /tmp/, like vx.$RANDOM.$RANDOM.$RANDOM.$$ on system startup. DESCRIPTION: In general the startup scripts should call quit(), in which it call do the cleanup when errors detected. The scripts were calling exit() directly instead of quit() leaving some random-created directories uncleaned. RESOLUTION: These script should be restored to call quit() instead of exit() directly. * INCIDENT NO:2737373 TRACKING ID:2556467 SYMPTOM: When dmp_native_support is enabled, ASM (Automatic Storage Management) disks are disconnected from host and host is rebooted, user defined user-group ownership of respective DMP (Dynamic Multipathing) devices is lost and ownership is set to default values. DESCRIPTION: The user-group ownership records of DMP devices in /etc/vx/.vxdmprawdev file are refreshed at the time of boot and only the records of currently available devices are retained. As part of refresh, records of all the disconnected ASM disks are removed from /etc/vx/.vxdmpraw and hence set to default value. RESOLUTION: Made code changes so that the file /etc/vx/.vxdmprawdev will not be refreshed at boot time. * INCIDENT NO:2747340 TRACKING ID:2739709 SYMPTOM: While rebuilding disk group,maker file generated from "vxprint - dmvpshrcCx -D -" command does not have the links between volumes and vset. Hence,rebuild of disk group fails. DESCRIPTION: File generated by the "vxprint -dmvpshrcCx -D -" command does not have the link between volumes and vset(volume set) due to which diskgroup rebuilding fails. RESOLUTION: Code changes are done to maintain the link between volumes and vsets. * INCIDENT NO:2759895 TRACKING ID:2753954 SYMPTOM: When cable is disconnected from one port of a dual-port FC HBA, only paths going through the port should be marked as SUSPECT. But paths going through other port are also getting marked as SUSPECT. DESCRIPTION: Disconnection of a cable from a HBA port generates a FC event. When the event is generated, paths of all ports of the corresponding HBA are marked as SUSPECT. RESOLUTION: The code changes are done to mark the paths only going through the port on which FC event is generated. * INCIDENT NO:2763211 TRACKING ID:2763206 SYMPTOM: vxdisk rm dumps core with following stack trace vfprintf volumivpfmt volpfmt do_rm DESCRIPTION: While copying the disk name of very large length array bound checking is not done which causes buffer overflow. Segmentation fault occurs while accessing corrupted memory, terminating "vxdisk rm" process. RESOLUTION: Code changes are done to do array bound checking to avoid such buffer overflow issues. * INCIDENT NO:2768492 TRACKING ID:2277558 SYMPTOM: vxassist outputs an error message while doing snapshot related operations. The message looks like : "VxVM VVR vxassist ERROR V-5-1-10127 getting associations of rvg : Property not found in the list" DESCRIPTION: The error message is being displayed incorrectly. There is an error condition which is getting masked by a previously occurred error which vxassist chose to ignore, and went ahead with the operation. RESOLUTION: Fix has been added to reset previously occurred error which has been ignored, so that the real error is displayed by vxassist. * INCIDENT NO:2802370 TRACKING ID:2585239 SYMPTOM: On a setup with tape devices, the VxVM commands like "vxdisk -o alldgs list" run very slow. DESCRIPTION: On a setup with tape devices, vxesd invokes HBA API even for tape devices in /dev/rtape directory, which slows down the system. RESOLUTION: Call HBA API only for /dev/[r]disk or /dev/[r]dsk devices. * INCIDENT NO:2804911 TRACKING ID:2637217 SYMPTOM: The storage allocation attributes 'pridiskname' and 'secdiskname' are not documented in the vradmin man page for resizevol/resizesrl. DESCRIPTION: The 'pridiskname' and 'secdiskname' are optional arguments to the vradmin resizevol and vradmin resizesrl commands, which enable users to specify a comma- separated list of disk names for the resize operation on a VVR data volume and SRL, respectively. These arguments were introduced in 5.1SP1, but were not documented in the vradmin man page. RESOLUTION: The vradmin man page has been updated to document the storage allocation attributes 'pridiskname' and 'secdiskname' for the vradmin resizevol and vradmin resizesrl commands. * INCIDENT NO:2821143 TRACKING ID:1431223 SYMPTOM: "vradmin syncvol" and "vradmin syncrvg" commands do not work if the remote diskgroup and vset names are specified when synchronizing vsets. DESCRIPTION: When command "vradmin syncvol" or "vradmin syncrvg" for vset is executed, vset is expanded to its component volumes and path is generated for each component volume. But when remote vset names are specified on command line, it fails to expand remote component volumes correctly. Synchronization will fail because of incorrect path for volumes. RESOLUTION: Code changes have been made to ensure remote vset is expanded correctly when specified on command line. * INCIDENT NO:2821452 TRACKING ID:2495332 SYMPTOM: vxcdsconvert(1M) fails if private region length is less than 1MB and it is a single sub-disk spanning the entire disk with following error: # vxcdsconvert -g alldisks evac_subdisks_ok=yes VxVM vxprint ERROR V-5-1-924 Record not found VxVM vxprint ERROR V-5-1-924 Record not found VxVM vxcdsconvert ERROR V-5-2-3174 Internal Error VxVM vxcdsconvert ERROR V-5-2-3120 Conversion process aborted DESCRIPTION: If non-cds disk private region length is less than 1MB, vxcdsconvert internally tries to relocate subdisks at the start to create room for the private region of 1MB. To make room for back-up labels, vxcdsconvert tries to relocate subdisks at the end of the disk. Two entries, one for relocation at the start and one at the end are created during the analysis phase. Once the first sub-disk is relocated, next vxprint operation fails as the sub-disk has already been evacuated to another DM(disk media record). RESOLUTION: This problem is fixed by allowing generation of multiple relocation entries for same subdisk. Later if the sub-disk is found to be already evacuated to other DM, relocation is skipped for the subdisk with same name. * INCIDENT NO:2821515 TRACKING ID:2617277 SYMPTOM: Man pages missing for the vxautoanalysis and vxautoconvert commands. DESCRIPTION: The man pages for the vxautoanalysis and vxautoconvert commands are missing from the base package. RESOLUTION: Added the man pages for vxautoanalysis(1M) and vxautoconvert(1M) commands. * INCIDENT NO:2821537 TRACKING ID:2792748 SYMPTOM: In an HPUX cluster environment, the slave join fails with the following error message in syslog: VxVM vxconfigd ERROR V-5-1-5784 cluster_establish:kernel interrupted vold on overlapping reconfig. DESCRIPTION: During the join, the slave node performs disk group import. As part of the import, the file descriptor pertaining to "Port u" is closed because of a wrong assignment of the return value of open(). Hence, the subsequent write to the same port was returning EBADF. RESOLUTION: Code changes are done to avoid closing the wrong file descriptor * INCIDENT NO:2821678 TRACKING ID:2389554 SYMPTOM: The vxdg command of VxVM (Veritas Volume Manager) located at /usr/sbin directory shows incorrect message for ssb (Serial Split Brain) information of a disk group. The ssb information uses "DISK PRIVATE PATH" as an item, but the content is public path of some disk. The ssb information also prints unknown characters to represent the config copy id of a disk if the disk's config copies are all disabled. Moreover, there is some redundant information in the output messages. "DISK PRIVATE PATH" error is like this: $ vxdisk list ... pubpaths: block=/dev/vx/dmp/s4 char=/dev/vx/rdmp/s4 privpaths: block=/dev/vx/dmp/s3 char=/dev/vx/rdmp/s3 ... $ vxsplitlines -v -g mydg ... Pool 0 DEVICE DISK DISK ID DISK PRIVATE PATH /dev/vx/rdmp/s4 Unknown character error message is like this: $ vxdg import ... To import the diskgroup with config copy from the second pool issue the command /usr/sbin/vxdg [-s] -o selectcp= import ... DESCRIPTION: VxVM uses a SSB data structure to maintain ssb information displayed to the user. The SSB data structure contains some members, such as Pool ID, config copy id, etc. After memory allocation for a SSB data structure, this new allocated memory area is not initialized. If all the config copies of some disk are disabled, then the config copy id member has unknwon data. vxdg command will try to print such data, then unknown characters are displayed to the stdout. The SSB data structure has "disk public path" member, but no "disk private path" member. So the output message can only display public path of a disk. RESOLUTION: The ssb structure has been changed to use "disk private path" instead of "disk public path". Moreover, after memory allocation for a ssb structure, newly allocated memory is properly initialized. * INCIDENT NO:2826129 TRACKING ID:2826125 SYMPTOM: VxVM script daemons are not up after they are invoked with the vxvm-recover script. DESCRIPTION: When the VxVM script daemon is starting, it will terminate any stale instance if it does exist. When the script daemon is invoking with exactly the same process id of the previous invocation, the daemon itself is abnormally terminated by killing one own self through a false-positive detection. RESOLUTION: Code changes was made to handle the same process id situation correctly. * INCIDENT NO:2826607 TRACKING ID:1675482 SYMPTOM: vxdg list command shows configuration copy in new failed state. # vxdg list dgname config disk 3PARDATA0_75 copy 1 len=48144 state=new failed config-tid=0.1550 pending-tid=0.1551 Error: error=Volume error 0 DESCRIPTION: When a configuration copy is initialized on a new disk in a diskgroup, an IO error on the disk can prevent on-disk update and make configuration copy in- consistent. RESOLUTION: In case of a failed initialization, configuration copy is disabled. If required in future, this disabled copy will be reused for setting up a new configuration copy. If current state of configuration copy is "new-failed", next import of the diskgroup will disable it. * INCIDENT NO:2827939 TRACKING ID:2088426 SYMPTOM: Re-onlining of all disks irrespective of whether they belong to the shared dg being destroyed/deported is being done on master and slaves. DESCRIPTION: When a shared dg is destroyed/deported, all disks on the nodes in the cluster are re-onlined asynchronously when another command is fired. This results in wasteful usage of resources and delaying the next command substantially based on how many disks/luns are there on each node. RESOLUTION: Restrict re-onlining of luns/disks to those that belong to the dg that is being destroyed/deported. By doing this resource and delay in the next command is restricted to the number of luns/disks that belong to the dg in question. * INCIDENT NO:2836910 TRACKING ID:2818840 SYMPTOM: 1. The file permissions set to ASM devices is not persistent across reboot. 2. User is not able to set desired permissions to ASM devices. 3. The files created with user id "root" and group other than "system" are not persistent. DESCRIPTION: The vxdmpasm sets the permissions of the devices to "660", which is not persistent across reboot as these devices are not kept in /etc/vx/.vxdmpasmdev file. Currently there is no option which enables the User to set the desired permissions. The files created with user id root and group other than "system" are changed back to "root:system" upon reboot. RESOLUTION: Code is modified to keep the device entries in the file /etc/vx/.vxdmpasmdev to make the permissions persistent across reboot. Code is enhanced to provide an option to set the desired permissions and set the desired user id/group. * INCIDENT NO:2852270 TRACKING ID:2715129 SYMPTOM: Vxconfigd hangs during Master takeover in a CVM (Clustered Volume Manager) environment. This results in vx command hang. DESCRIPTION: During Master takeover, VxVM (Veritas Volume Manager) kernel signals Vxconfigd with the information of new Master. Vxconfigd then proceeds with a vxconfigd- level handshake with the nodes across the cluster. Before kernel could signal to vxconfigd, vxconfigd handshake mechanism got started, resulting in the hang. RESOLUTION: Code changes are done to ensure that vxconfigd handshake gets started only upon receipt of signal from the kernel. * INCIDENT NO:2858859 TRACKING ID:2858853 SYMPTOM: In CVM(Cluster Volume Manager) environment, after master switch, vxconfigd dumps core on the slave node (old master) when a disk is removed from the disk group. dbf_fmt_tbl() voldbf_fmt_tbl() voldbsup_format_record() voldb_format_record() format_write() ddb_update() dg_set_copy_state() dg_offline_copy() dasup_dg_unjoin() dapriv_apply() auto_apply() da_client_commit() client_apply() commit() dg_trans_commit() slave_trans_commit() slave_response() fillnextreq() vold_getrequest() request_loop() main() DESCRIPTION: During master switch, disk group configuration copy related flags are not cleared on the old master, hence when a disk is removed from a disk group, vxconfigd dumps core. RESOLUTION: Necessary code changes have been made to clear configuration copy related flags during master switch. * INCIDENT NO:2859390 TRACKING ID:2000585 SYMPTOM: If 'vxrecover -sn' is run and at the same time one volume is removed, vxrecover exits with the error 'Cannot refetch volume', the exit status code is zero but no volumes are started. DESCRIPTION: vxrecover assumes that volume is missing because the diskgroup must have been deported while vxrecover was in progress. Hence, it exits without starting remaining volumes. vxrecover should be able to start other volumes, if the DG is not deported. RESOLUTION: Modified the source to skip missing volume and proceed with remaining volumes. * INCIDENT NO:2860449 TRACKING ID:2836798 SYMPTOM: 'vxdisk resize' fails with the following error on the simple format EFI (Extensible Firmware Interface) disk expanded from array side and system may panic/hang after a few minutes. # vxdisk resize disk_10 VxVM vxdisk ERROR V-5-1-8643 Device disk_10: resize failed: Configuration daemon error -1 DESCRIPTION: As VxVM doesn't support Dynamic Lun Expansion on simple/sliced EFI disk, last usable LBA (Logical Block Address) in EFI header is not updated while expanding LUN. Since the header is not updated, the partition end entry was regarded as illegal and cleared as part of partition range check. This inconsistent partition information between the kernel and disk causes system panic/hang. RESOLUTION: Added checks in VxVM code to prevent DLE on simple/sliced EFI disk. * INCIDENT NO:2860451 TRACKING ID:2815517 SYMPTOM: vxdg adddisk succeeds to add a clone disk to non-clone and non-clone disk to clone diskgroup, resulting in mixed diskgroup. DESCRIPTION: vxdg import fails for diskgroup which has mix of clone and non-clone disks. So vxdg adddisk should not allow creation of mixed diskgroup. RESOLUTION: vxdisk adddisk code is modified to return an error for an attempt to add clone disk to non-clone or non-clone disks to clone diskgroup, Thus it prevents addition of disk in diskgroup which leads to mixed diskgroup. * INCIDENT NO:2882488 TRACKING ID:2754819 SYMPTOM: Diskgroup rebuild through 'vxmake -d' gets stuck with following stack trace: buildlocks() MakeEverybody() main() DESCRIPTION: During diskgroup rebuild for configurations having multiple objects on a single cache object, an internal list of cache objects gets incorrectly modified to a circular list, which causes infinite looping during its access. RESOLUTION: Code changes are done to correctly populate the cache object list. * INCIDENT NO:2886083 TRACKING ID:2257850 SYMPTOM: Memory leak is observed when information about enclosure is accessed by vxdiskadm. DESCRIPTION: The memory allocated locally for a data structure keeping information about the array specific attributes is not freed. RESOLUTION: Code changes are made to avoid such memory leaks. * INCIDENT NO:2911009 TRACKING ID:2535716 SYMPTOM: LVM Volume Group (VG) to VxVM Disk Group conversion fails requesting user to reduce the number of configuration records. Following is an example of error messages seen during the conversion: Analysis of found insufficient Private Space for conversion SMALLEST VGRA space = 176 RESERVED space sectors = 78 PRIVATE SPACE/FREE sectors = 98 AVAILABLE sector space = 49 AVAILABLE sector bytes = 50176 RECORDS needed to convert = 399 MAXIMUM records allowable = 392 The smallest disk in the Volume Group () does not have sufficient private space for the conversion to succeed. There is only enough private space for 392 VM Database records and the conversion of Volume Group () would require enough space to allow 399 VxVM Database records. This would roughly translate to needing an additional 896 bytes available in the private space. This can be accomplished by reducing the number of volumes in the () Volume Group, and allowing that for every volume removed, the number of Database records required would be reduced by three. This is only a rough approximation, however. DESCRIPTION: Conversion process works in-place such that VXVM's public region is same as LVM public region, while VXVM creates the private region between the start of the disk and the start of the public region. In case the public region for LVM starts early on the disk and source LVM configuration contains very large number of records such that the space between the start of the disk and the start of the public region is not sufficient to hold the private region, conversion process fails. RESOLUTION: Conversion process now creates private region after the public region using the free PE's available in case enough space is not available between the start of the disk to the start of the public region. With this change, new behavior of vxvmconvert ensures that the conversion process succeeds in case at least one disk in the configuration is able to hold the private region either before or after the public region. Conversion process would now fail only if none of the disks in the source configuration is capable of holding private region anywhere on the disk. * INCIDENT NO:2911010 TRACKING ID:2627056 SYMPTOM: vxmake(1M) command when run with a very large DESCRIPTION: Due to a memory leak in vxmake(1M) command, data section limit for the process was reached. As a result further memory allocations failed and vxmake command failed with the above error RESOLUTION: Fixed the memory leak by freeing the memory after it has been used. PATCH ID:PHCO_42992 * INCIDENT NO:2621549 TRACKING ID:2621465 SYMPTOM: When a failed disk belongs to a site has once again become accessible, it cannot be reattached to the disk group. DESCRIPTION: As the disk has a site tag name set, 'vxdg adddisk' command invoked in 'vxreattach' command needs the option '-f' to add the disk back to the disk group. RESOLUTION: Add the option '-f' to 'vxdg adddisk' command when it is invoked in 'vxreattach' command. * INCIDENT NO:2626915 TRACKING ID:2417546 SYMPTOM: Raw devices are lost after OS rebooting and also cause permissions issue due to change in dmpnode permissions from 660 to 600. DESCRIPTION: On reboot, while creating raw devices we generate next available device number. There is counting bug due to which VxVM were ending up creating one less device. Also it was creating permissions issue due to change in dmpnode permissions. RESOLUTION: This issue is addressed by source change wherein correct counters are kept and device permissions are changed appropriately. * INCIDENT NO:2626920 TRACKING ID:2061082 SYMPTOM: "vxddladm -c assign names" command does not work if dmp_native_support tunable is enabled. DESCRIPTION: If dmp_native_support tunable is set to "on" then VxVM does not allow change in name of dmpnodes. This holds true even for device with native support not enabled like VxVM labeled or Third Party Devices. So there is no way for selectively changing name of devices for which native support is not enabled. RESOLUTION: This enhancement is addressed by code change to selectively change name for devices with native support not enabled. * INCIDENT NO:2643651 TRACKING ID:2643634 SYMPTOM: If standard(non-clone) disks and cloned disks of the same disk group are seen in a host, dg import will fail with the following error message when the standard(non-clone) disks have no enabled configuration copy of the disk group. # vxdg import VxVM vxdg ERROR V-5-1-10978 Disk group : import failed: Disk group has no valid configuration copies DESCRIPTION: When VxVM is importing such a mixed configuration of standard(non-clone) disks and cloned disks, standard(non-clone) disks will be selected as the member of the disk group in 5.0MP3RP5HF1 and 5.1SP1RP2. It will be done while administrators are not aware of the fact that there is a mixed configuration and the standard(non-clone) disks are to be selected for the import. It is hard to figure out from the error message and need time to investigate what is the issue. RESOLUTION: Syslog message enhancements are made in the code that administrators can figure out if such a mixed configuration is seen in a host and also which disks are selected for the import. * INCIDENT NO:2666175 TRACKING ID:2666163 SYMPTOM: A small memory leak may be seen in vxconfigd, the VxVM configuration daemon when Serial Split Brain(SSB) error is detected in the import process. DESCRIPTION: The leak may occur when Serial Split Brain(SSB) error is detected in the import process. It is because when the SSB error is returning from a function, a dynamically allocated memory area in the same function would not be freed. The SSB detection is a VxVM feature where VxVM detects if the configuration copy in the disk private region becomes stale unexpectedly. A typical use case of the SSB error is that a disk group is imported to different systems at the same time and configuration copy update in both systems results in an inconsistency in the copies. VxVM cannot identify which configuration copy is most up-to-date in this situation. As a result, VxVM may detect SSB error on the next import and show the details through a CLI message. RESOLUTION: Code changes are made to avoid the memory leak and also a small message fix has been done. * INCIDENT NO:2695225 TRACKING ID:2675538 SYMPTOM: Data corruption can be observed on a CDS (Cross-platform Data Sharing) disk, as part of LUN resize operations. The following pattern would be found in the data region of the disk. cyl alt 2 hd sec DESCRIPTION: The CDS disk maintains a SUN VTOC in the zeroth block and a backup label at the end of the disk. The VTOC maintains the disk geometry information like number of cylinders, tracks and sectors per track. The backup label is the duplicate of VTOC and the backup label location is determined from VTOC contents. As part of resize, VTOC is not updated to the new size, which results in the wrong calculation of the backup label location. If the wrongly calculated backup label location falls in the public data region rather than the end of the disk as designed, data corruption occurs. RESOLUTION: Update the VTOC contents appropriately for LUN resize operations to prevent the data corruption. * INCIDENT NO:2695227 TRACKING ID:2674465 SYMPTOM: Data corruption is observed when DMP node names are changed by following commands for DMP devices that are controlled by a third party multi-pathing driver (E.g. MPXIO and PowerPath ) # vxddladm [-c] assign names # vxddladm assign names file= # vxddladm set namingscheme= DESCRIPTION: The above said commands when executed would re-assign names to each devices. Accordingly the in-core DMP database should be updated for each device to map the new device name with appropriate device number. Due to a bug in the code, the mapping of names with the device number wasn't done appropriately which resulted in subsequent IOs going to a wrong device thus leading to data corruption. RESOLUTION: DMP routines responsible for mapping the names with right device number is modified to fix this corruption problem. * INCIDENT NO:2701152 TRACKING ID:2700486 SYMPTOM: If the VVR Primary and Secondary nodes have the same host-name, and there is a loss of heartbeats between them, vradmind daemon can core-dump if an active stats session already exists on the Primary node. Following stack-trace is observed: pthread_kill() _p_raise() raise.raise() abort() __assert_c99 StatsSession::sessionInitReq() StatsSession::processOpReq() StatsSession::processOpMsgs() RDS::processStatsOpMsg() DBMgr::processStatsOpMsg() process_message() main() DESCRIPTION: On loss of heartbeats between the Primary and Secondary nodes, and a subsequent reconnect, RVG information is sent to the Primary by Secondary node. In this case, if a Stats session already exists on the Primary, a STATS_SESSION_INIT request is sent back to the Secondary. However, the code was using "hostname" (as returned by `uname -a`) to identify the secondary node. Since both the nodes had the same hostname, the resulting STATS_SESSION_INIT request was received at the Primary itself, causing vradmind to core dump. RESOLUTION: Code was modified to use 'virtual host-name' information contained in the RLinks, rather than hostname(1m), to identify the secondary node. In a scenario where both Primary and Secondary have the same host-name, virtual host-names are used to configure VVR. * INCIDENT NO:2702110 TRACKING ID:2700792 SYMPTOM: vxconfigd, the VxVM volume configuration daemon may dump a core with the following stack during the Cluster Volume Manager(CVM) startup with "hares -online cvm_clus -sys [node]". dg_import_finish() dg_auto_import_all() master_init() role_assume() vold_set_new_role() kernel_get_cvminfo() cluster_check() vold_check_signal() request_loop() main() DESCRIPTION: During CVM startup, vxconfigd accesses the disk group record's pointer of a pending record while the transaction on the disk group is in progress. At times, vxconfigd incorrectly accesses the stale pointer while processing the current transaction, thus resulting in a core dump. RESOLUTION: Code changes are made to access the appropriate pointer of the disk group record which is active in the current transaction. Also, the disk group record is appropriately initialized to NULL value. * INCIDENT NO:2703370 TRACKING ID:2700086 SYMPTOM: In the presence of "Not-Ready" EMC devices on the system, multiple dmp (path disabled/enabled) events messages are seen in the syslog DESCRIPTION: The issue is that vxconfigd enables the BCV devices which are in Not-Ready state for IO as the SCSI inquiry succeeds, but soon finds that they cannot be used for I/O and disables those paths. This activity takes place whenever "vxdctl enable" or "vxdisk scandisks" command is executed. RESOLUTION: Avoid changing the state of the BCV device which is in "Not-Ready" to prevent IO and dmp event messages. * INCIDENT NO:2703373 TRACKING ID:2698860 SYMPTOM: Mirroring a large size VxVM volume comprising of THIN luns underneath and with VxFS filesystem atop mounted fails with the following error: Command error # vxassist -b -g $disk_group_name mirror $volume_name VxVM vxplex ERROR V-5-1-14671 Volume is configured on THIN luns and not mounted. Use 'force' option, to bypass smartmove. To take advantage of smartmove for supporting thin luns, retry this operation after mounting the volume. VxVM vxplex ERROR V-5-1-407 Attempting to cleanup after failure ... Truss output error: statvfs("", 0xFFBFEB54) Err#79 EOVERFLOW DESCRIPTION: The statvfs system call is invoked internally during mirroring operation to retrieve statistics information of VxFS file system hosted on the volume. However, since the statvfs system call only supports maximum 4294967295 (4GB-1) blocks, so if the total filesystem blocks are greater than that, EOVERFLOW error occurs. This also results in vxplex terminating with the errors. RESOLUTION: Use the 64 bits version of statvfs i.e., statvfs64 system call to resolve the EOVERFLOW and vxplex errors. * INCIDENT NO:2711758 TRACKING ID:2710579 SYMPTOM: Data corruption can be observed on a CDS (Cross-platform Data Sharing) disk, as part of operations like LUN resize, Disk FLUSH, Disk ONLINE etc. The following pattern would be found in the data region of the disk. cyl alt 2 hd sec DESCRIPTION: The CDS disk maintains a SUN VTOC in the zeroth block and a backup label at the end of the disk. The VTOC maintains the disk geometry information like number of cylinders, tracks and sectors per track. The backup label is the duplicate of VTOC and the backup label location is determined from VTOC contents. If the content of SUN VTOC located in the zeroth sector are incorrect, this may result in the wrong calculation of the backup label location. If the wrongly calculated backup label location falls in the public data region rather than the end of the disk as designed, data corruption occurs. RESOLUTION: Suppressed writing the backup label to prevent the data corruption. * INCIDENT NO:2744219 TRACKING ID:2729501 SYMPTOM: In Dynamic Multi pathing environment, excluding a path also excludes other set of paths with matching substrings. DESCRIPTION: excluding a path using vxdmpadm exclude vxvm path=<> is excluding all the paths with matching substring. This is due to strncmp() used for comparison. Also the size of h/w path defined in the structure is more than what is actually fetched. RESOLUTION: Correct the size of h/w path in the structure and use strcmp for comparison inplace of strncmp() * INCIDENT NO:2750454 TRACKING ID:2423701 SYMPTOM: Upgrade of VxVM caused change in permissions of /etc/vx/vxesd during live upgrade from drwx------ to d---r-x---. DESCRIPTION: '/etc/vx/vxesd' directory gets shipped in VxVM with "drwx------" permissions. However, while starting the vxesd daemon, if this directory is not present, it gets created with "d---r-x---". RESOLUTION: Changes are made so that while starting vxesd daemon '/etc/vx/vxesd' gets created with 'drwx------' permissions. * INCIDENT NO:2752178 TRACKING ID:2741240 SYMPTOM: In a VxVM environment, "vxdg join" when executed during heavy IO load fails with the below message. VxVM vxdg ERROR V-5-1-4597 vxdg join [source_dg] [target_dg] failed join failed : Commit aborted, restart transaction join failed : Commit aborted, restart transaction Half of the disks that were part of source_dg will become part of target_dg whereas other half will have no DG details. DESCRIPTION: In a vxdg join transaction, VxVM has implemented it as a two phase transaction. If the transaction fails after the first phase and during the second phase, half of the disks belonging to source_dg will become part of target_dg and the other half of the disks will be in a complex irrecoverable state. Also, in heavy IO situation, any retry limit (i.e.) a limit to retry transactions can be easily exceeded. RESOLUTION: "vxdg join" is now designed as a one phase atomic transaction and the retry limit is eliminated. PATCH ID:PHCO_42807 * INCIDENT NO:2477272 TRACKING ID:2169726 SYMPTOM: After import operation, the imported diskgroup contains combination of cloned and original disks. For example, after importing the diskgroup which has four disks, two of the disks from imported diskgroup are cloned disks and the other two are original disks. DESCRIPTION: For a particular diskgroup, if some of the original disks are not available at the time of diskgroup import operation and the corresponding cloned disks are present, then the diskgroup imported through vxdg import operation contains combination of cloned and original disks. Example - Diskgroup named dg1 with the disks disk1 and disk2 exists on some machine. Clones of disks named disk1_clone disk2_clone are also available. If disk2 goes offline and the import for dg1 is performed, then the resulting diskgroup will contain disks disk1 and disk2_clone. RESOLUTION: The diskgroup import operation will consider cloned disks only if no original disk is available. If any of the original disks exists at the time of import operation, then the import operation will be attempted using original disks only. * INCIDENT NO:2507120 TRACKING ID:2438426 SYMPTOM: The following messages are displayed after vxconfigd is started. pp_claim_device: Could not get device number for /dev/rdsk/emcpower0 pp_claim_device: Could not get device number for /dev/rdsk/emcpower1 DESCRIPTION: Device Discovery Layer(DDL) has incorrectly marked a path under dmp device with EFI flag even though there is no corresponding Extensible Firmware Interface (EFI) device in /dev/[r]dsk/. As a result, Array Support Library (ASL) issues a stat command on non-existent EFI device and displays the above messages. RESOLUTION: Avoided marking EFI flag on Dynamic MultiPathing (DMP) paths which correspond to non-efi devices. * INCIDENT NO:2508294 TRACKING ID:2419486 SYMPTOM: Data corruption is observed with single path when naming scheme is changed from enclodure based (EBN) to OS Native (OSN). DESCRIPTION: The Data corruption can occur in the following configuration, when the naming scheme is changed while applications are on-line. 1. The DMP device is configured with single path or the devices are controlled by Third party Multipathing Driver (Ex: MPXIO, MPIO etc.,) 2. The DMP device naming scheme is EBN (enclosure based naming) and persistence=yes 3. The naming scheme is changed to OSN using the following command # vxddladm set namingscheme=osn There is possibility of change in name of the VxVM device (DA record) while the naming scheme is changing. As a result of this the device attribute list is updated with new DMP device names. Due to a bug in the code which updates the attribute list, the VxVM device records are mapped to wrong DMP devices. Example: Following are the device names with EBN naming scheme. MAS-usp0_0 auto:cdsdisk hitachi_usp0_0 prod_SC32 online MAS-usp0_1 auto:cdsdisk hitachi_usp0_4 prod_SC32 online MAS-usp0_2 auto:cdsdisk hitachi_usp0_5 prod_SC32 online MAS-usp0_3 auto:cdsdisk hitachi_usp0_6 prod_SC32 online MAS-usp0_4 auto:cdsdisk hitachi_usp0_7 prod_SC32 online MAS-usp0_5 auto:none - - online invalid MAS-usp0_6 auto:cdsdisk hitachi_usp0_1 prod_SC32 online MAS-usp0_7 auto:cdsdisk hitachi_usp0_2 prod_SC32 online MAS-usp0_8 auto:cdsdisk hitachi_usp0_3 prod_SC32 online MAS-usp0_9 auto:none - - online invalid disk_0 auto:cdsdisk - - online disk_1 auto:none - - online invalid bash-3.00# vxddladm set namingscheme=osn The follwoing is after executing the above command. The MAS-usp0_9 is changed as MAS-usp0_6 and the following devices are changed accordingly. bash-3.00# vxdisk list DEVICE TYPE DISK GROUP STATUS MAS-usp0_0 auto:cdsdisk hitachi_usp0_0 prod_SC32 online MAS-usp0_1 auto:cdsdisk hitachi_usp0_4 prod_SC32 online MAS-usp0_2 auto:cdsdisk hitachi_usp0_5 prod_SC32 online MAS-usp0_3 auto:cdsdisk hitachi_usp0_6 prod_SC32 online MAS-usp0_4 auto:cdsdisk hitachi_usp0_7 prod_SC32 online MAS-usp0_5 auto:none - - online invalid MAS-usp0_6 auto:none - - online invalid MAS-usp0_7 auto:cdsdisk hitachi_usp0_1 prod_SC32 online MAS-usp0_8 auto:cdsdisk hitachi_usp0_2 prod_SC32 online MAS-usp0_9 auto:cdsdisk hitachi_usp0_3 prod_SC32 online c4t20000014C3D27C09d0s2 auto:none - - online invalid c4t20000014C3D26475d0s2 auto:cdsdisk - - online RESOLUTION: Code changes are made to update device attribute list correctly even if name of the VxVM device is changed while the naming scheme is changing. * INCIDENT NO:2511928 TRACKING ID:2420386 SYMPTOM: Corrupted data is seen near the end of a sub-disk, on thin-reclaimable disks with either CDS EFI or sliced disk formats. DESCRIPTION: In environments with thin-reclaim disks running with either CDS-EFI disks or sliced disks, misaligned reclaims can be initiated. In some situations, when reclaiming a sub-disk, the reclaim does not take into account the correct public region start offset, which in rare instances can potentially result in reclaiming data before the sub-disk which is being reclaimed. RESOLUTION: The public offset is taken into account when initiating all reclaim operations. * INCIDENT NO:2515137 TRACKING ID:2513101 SYMPTOM: When VxVM is upgraded from 4.1MP4RP2 to 5.1SP1RP1, the data on CDS disk gets corrupted. DESCRIPTION: When CDS disks are initialized with VxVM version 4.1MP4RP2, the number of cylinders are calculated based on the disk raw geometry. If the calculated number of cylinders exceed Solaris VTOC limit (65535), because of unsigned integer overflow, truncated value of number of cylinders gets written in CDS label. After the VxVM is upgraded to 5.1SP1RP1, CDS label gets wrongly written in the public region leading to the data corruption. RESOLUTION: The code changes are made to suitably adjust the number of tracks & heads so that the calculated number of cylinders be within Solaris VTOC limit. * INCIDENT NO:2517819 TRACKING ID:2530279 SYMPTOM: vxesd consumes 100% CPU, and hang is in following stack: vold_open () es_update_ddlconfig () do_get_ddl_config () start_ipc () main () DESCRIPTION: Due to inappropriate handling of thread control, race condition occurs inside the ESD code path. This race condition leads 100% CPU cycles and reaches to hang state. RESOLUTION: Done the proper way of handling to control thread to avoid the race condition in the code path. * INCIDENT NO:2525333 TRACKING ID:2148851 SYMPTOM: "vxdisk resize" operation fails on a disk with VxVM cdsdisk/simple/sliced layout on Solaris/Linux platform with the following message: VxVM vxdisk ERROR V-5-1-8643 Device emc_clariion0_30: resize failed: New geometry makes partition unaligned DESCRIPTION: The new cylinder size selected during "vxdisk resize" operation is unaligned with the partitions that existed prior to the "vxdisk resize" operation. RESOLUTION: The algorithm to select the new geometry has been redesigned such that the new cylinder size is always aligned with the existing as well as new partitions. * INCIDENT NO:2528144 TRACKING ID:2528133 SYMPTOM: vxprint -l command gives following error (along with the output), when multiple DGs have same DM_NAME VxVM vxdisk ERROR V-5-1-0 disk100 - Record in multiple disk groups DESCRIPTION: vxprint -l, internally takes one record(in this case DM_NAME) at a time and searches that record in all the DGs. If it finds the record in more than one DG, it marks the flag to DGL_MORE. This DGL_MORE flag checking was causing the error in case of vxprint -l. RESOLUTION: Since, it is a valid operation to create multiple DGs with same DM_NAME. The error checking is not required at all. The code change removes the flag checking logic from the function. * INCIDENT NO:2531993 TRACKING ID:2524936 SYMPTOM: Disk group is disabled after rescanning disks with "vxdctl enable" command. The error messages given below are seen in vxconfigd debug log output: VxVM vxconfigd ERROR V-5-1-12223 Error in claiming /dev/: The process file table is full. VxVM vxconfigd ERROR V-5-1-12223 Error in claiming /dev/: The process file table is full. ... VxVM vxconfigd ERROR V-5-1-12223 Error in claiming /dev/: The process file table is full. DESCRIPTION: When attachment of shared memory segment to the process address space fails, proper error handling of such case was missing in vxconfigd code, hence resulting in error in claiming disks and offlining configuration copies which in-turn results in disabling of disk group. RESOLUTION: Code changes are made to handle the failure case while creating shared memory segment. * INCIDENT NO:2574840 TRACKING ID:2344186 SYMPTOM: In a master-slave configuration with FMR3/DCO volumes, reboot of a cluster node fails to join back the cluster again with following error messages in the console [..] Jul XX 18:44:09 vienna vxvm:vxconfigd: [ID 702911 daemon.error] V-5-1-11092 cleanup_client: (Volume recovery in progress) 230 Jul XX 18:44:09 vienna vxvm:vxconfigd: [ID 702911 daemon.error] V-5-1-11467 kernel_fail_join() : Reconfiguration interrupted: Reason is retry to add a node failed (13, 0) [..] DESCRIPTION: VxVM volumes with FMR3/DCO have inbuilt DRL mechanism to track the disk block of in-flight IOs in order to recover the data much quicker in case of a node crash. Thus, a joining node awaits the variable, responsible for recovery, to get unset to join the cluster. However, due to a bug in FMR3/DCO code, this variable was set forever, thus leading to node join failure. RESOLUTION: Modified the FMR3/DCO code to appropriately set and unset this recovery variable. * INCIDENT NO:2676703 TRACKING ID:2553729 SYMPTOM: The following is observed during 'Upgrade' of VxVM (Veritas Volume Manager): i) 'clone_disk' flag is seen on non-clone disks in STATUS field when 'vxdisk -e list' is executed after uprade to 5.1SP1 from lower versions of VxVM. Eg: DEVICE TYPE DISK GROUP STATUS emc0_0054 auto:cdsdisk emc0_0054 50MP3dg online clone_disk emc0_0055 auto:cdsdisk emc0_0055 50MP3dg online clone_disk ii) Disk groups (dg) whose versions are less than 140 do not get imported after upgrade to VxVM versions 5.0MP3RP5HF1 or 5.1SP1RP2. Eg: # vxdg -C import VxVM vxdg ERROR V-5-1-10978 Disk group : import failed: Disk group version doesn't support feature; see the vxdg upgrade command DESCRIPTION: While uprading VxVM i) After upgrade to 5.1SP1 or higher versions: If a dg which is created on lower versions is deported and imported back on 5.1SP1 after the upgrade, then "clone_disk" flags gets set on non-cloned disks because of the design change in UDID (unique disk identifier) of the disks. ii) After upgrade to 5.0MP3RP5HF1 or 5.1SP1RP2: Import of dg with versions less than 140 fails. RESOLUTION: Code changes are made to ensure that: i) clone_disk flag does not get set for non-clone disks after the upgrade. ii) Disk groups with versions less than 140 get imported after the upgrade. PATCH ID:PHCO_42245 * INCIDENT NO:2163809 TRACKING ID:2151894 SYMPTOM: Internal testing utility volassert prints a message: Volume TCv1-548914: recover_offset=0, expected 1024 DESCRIPTION: We changed the behavior of recover_offset in other incident by resetting it back to zero after starting a volume. This works okay for normal cases but not for raid5 volumes. RESOLUTION: Recover offset will be set at the end of a volume after grow/init operations. * INCIDENT NO:2198041 TRACKING ID:2196918 SYMPTOM: When creating a space-opimized snapshot by specifying cache-object size either in percentage terms of the volume size or an absolute size, the snapshot creation can fail with an error similar to following: "VxVM vxassist ERROR V-5-1-10127 creating volume snap-dvol2-CV01: Volume or log length violates disk group alignment" DESCRIPTION: VxVM expects all virtual storage objects to have size aligned to a value which is set diskgroup-wide. One can get this value with: # vxdg list testdg|grep alignment alignment: 8192 (bytes) When the cachesize is specified in percentage, the value might not align with dg alignment. If not aligned, the creation of the cache-volume could fail with specified error message RESOLUTION: After computing the cache-size from specified percentage value, it is aligned up to the diskgroup alignment value before trying to create the cache-volume. * INCIDENT NO:2204146 TRACKING ID:2200670 SYMPTOM: Some disks are left detached and not recovered by vxattachd. DESCRIPTION: If the shared disk group is not imported or node is not part of the cluster when storage connectivity to failed node is restored, the vxattachd daemon does not getting notified about storage connectivity restore and does not trigger a reattach. Even if the disk group is later imported or the node is joined to CVM cluster, the disks are not automatically reattached. RESOLUTION: i) Missing events for a deported diskgroup: The fix handles this by listening to the import event of the diksgroup and triggers the brute-force recovery for that specific diskgroup. ii) parallel recover of volumes from same disk: vxrecover automatically serializes the recovery of objects that are from the same disk to avoid the back and forth head movements. Also provided an option in vxattchd and vxrecover to control the number of parallel recovery that can happen for objects from the same disk. * INCIDENT NO:2214184 TRACKING ID:2202710 SYMPTOM: Transactions on Rlink are not allowed during SRL to DCM flush. DESCRIPTION: Present implementation doesn't allow rlink transaction to go through if SRL to DCM flush is in progress. As SRL overflows, VVR start reading from SRL and mark the dirty regions in corresponding DCMs of data volumes, it is called SRL to DCM flush. During SRL to DCM flush transactions on rlink is not allowed. Time to complete SRL flush depend on SRL size, it could range from minutes to many hours. If user initiate any transaction on rlink then it will hang until SRL flush completes. RESOLUTION: Changed the code behavior to allow rlink transaction during SRL flush. Fix stops the SRL flush for transaction to go ahead and restart the flush after transaction completion. * INCIDENT NO:2232829 TRACKING ID:2232789 SYMPTOM: With NetApp metro cluster disk arrays, takeover operations (toggling of LUN ownership within NetApp filer) can lead to IO failures on VxVM volumes. Example of an IO error message at VxVM VxVM vxio V-5-0-2 Subdisk disk_36-03 block 24928: Uncorrectable write error DESCRIPTION: During the takeover operation, the array fails the PGR and IO SCSI commands on secondary paths with the following transient error codes - 0x02/0x04/0x0a (NOT READY/LOGICAL UNIT NOT ACCESSIBLE, ASYMMETRIC ACCESS STATE TRANSITION) or 0x02/0x04/0x01 (NOT READY/LOGICAL UNIT IS IN PROCESS OF BECOMING READY) - that are not handled properly within VxVM. RESOLUTION: Included required code logic within the APM so that the SCSI commands with transient errors are retried for the duration of NetApp filer reconfig time (60 secs) before failing the IO's on VxVM volumes. * INCIDENT NO:2234292 TRACKING ID:2152830 SYMPTOM: Sometimes the storage admins create multiple copies/clones of the same device. Diskgroup import fails with a non-descriptive error message when multiple copies(clones) of the same device exists and original device(s) are either offline or not available. # vxdg import mydg VxVM vxdg ERROR V-5-1-10978 Disk group mydg: import failed: No valid disk found containing disk group DESCRIPTION: If the original devices are offline or unavailable, vxdg import picks up cloned disks for import. DG import fails by design unless the clones are tagged and tag is specified during DG import. While the import failure is expected, but the error message is non-descriptive and doesn't provide any corrective action to be taken by user. RESOLUTION: Fix has been added to give correct error meesage when duplicate clones exist during import. Also, details of duplicate clones is reported in the syslog. Example: [At CLI level] # vxdg import testdg VxVM vxdg ERROR V-5-1-10978 Disk group testdg: import failed: DG import duplcate clone detected [In syslog] vxvm:vxconfigd: warning V-5-1-0 Disk Group import failed: Duplicate clone disks are detected, please follow the vxdg (1M) man page to import disk group with duplicate clone disks. Duplicate clone disks are: c2t20210002AC00065Bd0s2 : c2t50060E800563D204d1s2 c2t50060E800563D204d0s2 : c2t50060E800563D204d1s2 * INCIDENT NO:2241149 TRACKING ID:2240056 SYMPTOM: 'vxdg move/split/join' may fail during high I/O load. DESCRIPTION: During heavy I/O load 'dg move' transcation may fail because of open/close assertion and retry will be done. As the retry limit is set to 30 'dg move' fails if retry hits the limit. RESOLUTION: Change the default transaction retry to unlimit, introduce a new option to 'vxdg move/split/join' to set transcation retry limit as follows: vxdg [-f] [-o verify|override] [-o expand] [-o transretry=retrylimit] move src_diskgroup dst_diskgroup objects ... vxdg [-f] [-o verify|override] [-o expand] [-o transretry=retrylimit] split src_diskgroup dst_diskgroup objects ... vxdg [-f] [-o verify|override] [-o transretry=retrylimit] join src_diskgroup dst_diskgroup * INCIDENT NO:2247645 TRACKING ID:2243044 SYMPTOM: Initialization of VxVM cdsdisk layout on a disk with greater than or equal to 1 TB fails on HP-UX/ia-64 platform. DESCRIPTION: During the initialization of VxVM cdsdisk layout on a disk with size greater than or equal to 1 TB on HP-UX/ia-64 platform, we were checking if the disk has an existing HP-UX LVM layout. During this check, the i/o was performed incorrectly using the DMP (Dynamic Multi-Pathing Driver) paths associated with the existing GPT partitions on the disk. RESOLUTION: This issue has been resolved by performing i/o to the whole device path during the initialization of VxVM cdsdisk layout on a disk with size greater than or equal to 1 TB. * INCIDENT NO:2253269 TRACKING ID:2263317 SYMPTOM: vxdg(1M) man page does not clearly describe diskgroup import and destroy operations for the case in which original diskgroup is destroyed and cloned disks are present. DESCRIPTION: Diskgroup import with dgid is cosidered as a recovery operation. Therefore, while importing with dgid, even though the original diskgroup is destroyed, both the original as well as cloned disks are considered as available disks. Hence, the original diskgroup is imported in such a scenario. The existing vxdg(1M) man page does not clearly describe this scenario. RESOLUTION: Modified the vxdg(1M) man page to clearly describe the scenario. * INCIDENT NO:2256728 TRACKING ID:2248730 SYMPTOM: Command hungs if "vxdg import" called from script with STDERR redirected. DESCRIPTION: If script is having "vxdg import" with STDERR redirected then script does not finish till DG import and recovery is finished. Pipe between script and vxrecover is not closed properly which keeps calling script waiting for vxrecover to complete. RESOLUTION: Closed STDERR in vxrecover and redirected the output to /dev/console. * INCIDENT NO:2316309 TRACKING ID:2316297 SYMPTOM: The following error messages are printed on the console every time system boots. VxVM vxdisk ERROR V-5-1-534 Device [DEVICE NAME]: Device is in use DESCRIPTION: During system boot up, while Volume Manager diskgroup imports, vxattachd daemon tries to online the disk. Since the disk may be already online sometimes, an attempt to re-online disk gives the below error message: VxVM vxdisk ERROR V-5-1-534 Device [DEVICE NAME]: Device is in use RESOLUTION: The solution is to check if the disk is already in "online" state. If so, avoid reonline. * INCIDENT NO:2323999 TRACKING ID:2323925 SYMPTOM: If the rootdisk is under VxVM control and /etc/vx/reconfig.d/state.d/install-db file exists, the following messages are observed on the console: UX:vxfs fsck: ERROR: V-3-25742: /dev/vx/dsk/rootdg/homevol:sanity check failed: cannot open /dev/vx/dsk/rootdg/homevol: No such device or address UX:vxfs fsck: ERROR: V-3-25742: /dev/vx/dsk/rootdg/optvol:sanity check failed: cannot open /dev/vx/dsk/rootdg/optvol: No such device or address DESCRIPTION: In the vxvm-startup script, there is check for the /etc/vx/reconfig.d/state.d/install-db file. If the install-db file exist on the system, the VxVM assumes that volume manager is not configured and does not start volume configuration daemon "vxconfigd". "install-db" file somehow existed on the system for a VxVM rootable system, this causes the failure. RESOLUTION: If install-db file exists on the system and the system is VxVM rootable, the following warning message is displayed on the console: "This is a VxVM rootable system. Volume configuration daemon could not be started due to the presence of /etc/vx/reconfig.d/state.d/install-db file. Remove the install-db file to proceed" * INCIDENT NO:2328219 TRACKING ID:2253552 SYMPTOM: vxconfigd leaks memory while reading the default tunables related to smartmove (a VxVM feature). DESCRIPTION: In Vxconfigd, memory allocated for default tunables related to smartmove feature is not freed causing a memory leak. RESOLUTION: The memory is released after its scope is over. * INCIDENT NO:2328286 TRACKING ID:2244880 SYMPTOM: Initialization of VxVM cdsdisk layout on a disk with size greater than or equal to 1 TB fails. DESCRIPTION: During the initialization of VxVM cdsdisk layout on a disk with size greater than or equal to 1 TB, alternative (backup) GPT label is written in the last 33 sectors of the disk. SCSI pass-thru mode was used to write the alternative GPT label. SCSI pass-thru mode could not handle device offsets equal to or greater than 1 TB RESOLUTION: This issue has been resolved by using the posix system calls to write the alternative GPT label during initialization of VxVM cdsdisk layout. * INCIDENT NO:2337091 TRACKING ID:2255182 SYMPTOM: If EMC CLARiiON arrays are configured with different failovermode for each host controllers ( e.g. one HBA has failovermode set as 1 while the other as 2 ), then VxVM's vxconfigd demon dumps core. DESCRIPTION: DDL (VxVM's Device Discovery Layer) determines the array type depending on the failovermode setting. DDL expects the same array type to be returned across all the paths going to that array. This fundamental assumption of DDL will be broken with different failovermode settings thus leading to vxconfigd core dump. RESOLUTION: Validation code is added in DDL to detect such configurations and emit appropriate warning messages to the user to take corrective actions and skips the later set of paths that are reporting different array type. * INCIDENT NO:2349653 TRACKING ID:2349352 SYMPTOM: Data corruption is observed on DMP(Dynamic Multipathing) device with single path during Storage reconfiguration (LUN addition/removal). DESCRIPTION: Data corruption can occur in the following configuration, when new LUNs are provisioned or removed under VxVM, while applications are on-line. 1. The DMP device naming scheme is EBN (enclosure based naming) and persistence=no 2. The DMP device is configured with single path or the devices are controlled by Third Party Multipathing Driver (Ex: MPXIO, MPIO etc.,) There is a possibility of change in name of the VxVM devices (DA record), when LUNs are removed or added followed by the following commands, since the persistence naming is turned off. (a) vxdctl enable (b) vxdisk scandisks Execution of above commands discovers all the devices and rebuilds the device attribute list with new DMP device names. The VxVM device records are then updated with this new attributes. Due to a bug in the code, the VxVM device records are mapped to wrong DMP devices. Example: Following are the device before adding new LUNs. sun6130_0_18 auto:cdsdisk disk_0 prod_SC32 online nohotuse sun6130_0_19 auto:cdsdisk disk_1 prod_SC32 online nohotuse The following are after adding new LUNs sun6130_0_18 auto - - nolabel sun6130_0_19 auto - - nolabel sun6130_0_20 auto:cdsdisk disk_0 prod_SC32 online nohotuse sun6130_0_21 auto:cdsdisk disk_1 prod_SC32 online nohotuse The name of the VxVM device sun6130_0_18 is changed to sun6130_0_20. RESOLUTION: The code that updates the VxVM device records is rectified. * INCIDENT NO:2353327 TRACKING ID:2179259 SYMPTOM: When using disks of size > 2TB and the disk encounters a media error with offset > 2TB while the disk responds to SCSI inquiry, data corruption can occur incase of a write operation DESCRIPTION: The I/O rety logic in DMP assumes that the I/O offset is within 2TB limit and hence when using disks of size > 2TB and the disk encounters a media error with offset > 2TB while the disk responds to SCSI inquiry, the I/O would be issued on a wrong offset within the 2TB range causing data corruption incase of write I/Os. RESOLUTION: The fix for this issue to change the I/O retry mechanism to work for >2TB offsets as well so that no offset truncation happens that could lead to data corruption * INCIDENT NO:2353328 TRACKING ID:2194685 SYMPTOM: vxconfigd dumps core in scenario where array side ports are disabled/enabled in loop for some iterations. gdb) where #0 0x081ca70b in ddl_delete_node () #1 0x081cae67 in ddl_check_migration_of_devices () #2 0x081d0512 in ddl_reconfigure_all () #3 0x0819b6d5 in ddl_find_devices_in_system () #4 0x0813c570 in find_devices_in_system () #5 0x0813c7da in mode_set () #6 0x0807f0ca in setup_mode () #7 0x0807fa5d in startup () #8 0x08080da6 in main () DESCRIPTION: Due to disabling the array side ports, the secondary paths get removed. But the primary paths are reusing the devno of the removed secondary paths which is not correctly handled in current migration code. Due to this, the DMP database gets corrupted and subsequent discoveries lead to configd core dump. RESOLUTION: The issue is due to incorrect setting of a DMP flag. The flag settting has been fixed to prevent the DMP database from corruption in the mentioned scenario. * INCIDENT NO:2353403 TRACKING ID:2337694 SYMPTOM: "vxdisk -o thin list" displays size as 0 for thin luns of capacity greater than 2 TB. DESCRIPTION: SCSI READ CAPACITY ioctl is invoked to get the disk capacity. SCSI READ CAPACITY returns data in extended data format if a disk capacity is 2 TB or greater. This extended data was parsed incorectly while calculating the disk capacity. RESOLUTION: This issue has been resolved by properly parsing the extended data returned by SCSI READ CAPACITY ioctl for disks of size greater than 2 TB or greater. * INCIDENT NO:2353404 TRACKING ID:2334757 SYMPTOM: Vxconfigd consumes a lot of memory when the DMP tunable dmp_probe_idle_lun is set on. "pmap" command on vxconfigd process shows continuous growing heap. DESCRIPTION: DMP path restoration daemon probes idle LUNs(Idle LUNs are VxVM disks on which no I/O requests are scheduled) and generates notify events to vxconfigd. Vxconfigd in turn send the nofification of these events to its clients. For any reasons, if vxconfigd could not deliver these events (because client is busy processing earlier sent event), it keeps these events to itself. Because of this slowness of events consumption by its clients, memory consumption of vxconfigd grows. RESOLUTION: dmp_probe_idle_lun is set to off by default. * INCIDENT NO:2353421 TRACKING ID:2334534 SYMPTOM: In CVM (Cluster Volume Manager) environment, a node (SLAVE) join to the cluster is getting stuck and leading to unending join hang unless join operation is stopped on joining node (SLAVE) using command '/opt/VRTS/bin/vxclustadm stopnode'. While CVM join is hung in user-land (also called as vxconfigd level join), on CVM MASTER node, vxconfigd (Volume Manager Configuration daemon) doesn't respond to any VxVM command, which communicates to vxconfigd process. When vxconfigd level CVM join is hung in user-land, "vxdctl -c mode" on joining node (SLAVE) displays an output such as: bash-3.00# vxdctl -c mode mode: enabled: cluster active - SLAVE master: mtvat1000-c1d state: joining reconfig: vxconfigd in join DESCRIPTION: As part of a CVM node join to the cluster, every node in the cluster updates the current CVM membership information (membership information which can be viewed by using command '/opt/VRTS/bin/vxclustadm nidmap') in kernel first and then sends a signal to vxconfigd in user land to use that membership in exchanging configuration records among each others. Since each node receives the signal (SIGIO) from kernel independently, the joining node's (SLAVE) vxconfigd is ahead of the MASTER in its execution. Thus any requests coming from the joining node (SLAVE) is denied by MASTER with the error "VE_CLUSTER_NOJOINERS" i.e. join operation is not currently allowed (error number: 234) since MASTER's vxconfigd has not got the updated membership from the kernel yet. While responding to joining node (SLAVE) with error "VE_CLUSTER_NOJOINERS", if there is any change in current membership (change in CVM node ID) as part of node join then MASTER node is wrongly updating the internal data structure of vxconfigd, which is being used to send response to joining (SLAVE) nodes. Due to wrong update of internal data structure, later when the joining node retries its request, the response from master is sent to a wrong node, which doesn't exist in the cluster, and no response is sent to the joining node. Joining node (SLAVE) never gets the response from MASTER for its request and hence CVM node join is not completed and leading to cluster hang. RESOLUTION: vxconfigd code is modified to handle the above mentioned scenario effectively. vxconfid on MASTER node will process connection request coming from joining node (SLAVE) effectively only when MASTER node gets the updated CVM membership information from kernel. * INCIDENT NO:2353425 TRACKING ID:2320917 SYMPTOM: vxconfigd, the VxVM configuration daemon dumps core and loses disk group configuration while invoking the following VxVM reconfiguration steps: 1) Volumes which were created on thin reclaimable disks are deleted. 2) Before the space of the deleted volumes is reclaimed, the disks (whose volume is deleted) are removed from the DG with 'vxdg rmdisk' command using '- k' option. 3) The disks are removed using 'vxedit rm' command. 4) New disks are added to the disk group using 'vxdg addisk' command. The stack trace of the core dump is : [ 0006f40c rec_lock3 + 330 0006ea64 rec_lock2 + c 0006ec48 rec_lock2 + 1f0 0006e27c rec_lock + 28c 00068d78 client_trans_start + 6e8 00134d00 req_vol_trans + 1f8 00127018 request_loop + adc 000f4a7c main + fb0 0003fd40 _start + 108 ] DESCRIPTION: When a volume is deleted from a disk group that uses thin reclaim luns, subdisks are not removed immediately, rather it is marked with a special flag. The reclamation happens at a scheduled time every day. "vxdefault" command can be invoked to list and modify the settings. After the disk is removed from disk group using 'vxdg -k rmdisk' and 'vxedit rm' command, the subdisks records are still in core database and they are pointing to disk media record which has been freed. When the next command is run to add another new disk to the disk group, vxconfigd dumps core when locking the disk media record which has already been freed. The subsequent disk group deport and import commands erase all disk group configuration as it detects an invalid association between the subdisks and the removed disk. RESOLUTION: 1) The following message will be printed when 'vxdg rmdisk' is used to remove disk that has reclaim pending subdisks: VxVM vxdg ERROR V-5-1-0 Disk is used by one or more subdisks which are pending to be reclaimed. Use "vxdisk reclaim " to reclaim space used by these subdisks, and retry "vxdg rmdisk" command. Note: reclamation is irreversible. 2) Add a check when using 'vxedit rm' to remove disk. If the disk is in removed state and has reclaim pending subdisks, following error message will be printed: VxVM vxedit ERROR V-5-1-10127 deleting : Record is associated * INCIDENT NO:2353427 TRACKING ID:2337353 SYMPTOM: The "vxdmpadm include" command is including all the excluded devices along with the device given in the command. Example: # vxdmpadm exclude vxvm dmpnodename=emcpower25s2 # vxdmpadm exclude vxvm dmpnodename=emcpower24s2 # more /etc/vx/vxvm.exclude exclude_all 0 paths emcpower24c /dev/rdsk/emcpower24c emcpower25s2 emcpower10c /dev/rdsk/emcpower10c emcpower24s2 # controllers # product # pathgroups # # vxdmpadm include vxvm dmpnodename=emcpower24s2 # more /etc/vx/vxvm.exclude exclude_all 0 paths # controllers # product # pathgroups # DESCRIPTION: When a dmpnode is excluded, an entry is made in /etc/vx/vxvm.exclude file. This entry has to be removed when the dmpnode is included later. Due to a bug in comparison of dmpnode device names, all the excluded devices are included. RESOLUTION: The bug in the code which compares the dmpnode device names is rectified. * INCIDENT NO:2353464 TRACKING ID:2322752 SYMPTOM: Duplicate device names are observed for NR (Not Ready) devices, when vxconfigd is restarted (vxconfigd -k). # vxdisk list emc0_0052 auto - - error emc0_0052 auto:cdsdisk - - error emc0_0053 auto - - error emc0_0053 auto:cdsdisk - - error DESCRIPTION: During vxconfigd restart, disk access records are rebuilt in vxconfigd database. As part of this process IOs are issued on all the devices to read the disk private regions. The failure of these IOs on NR devicess resulted in creating duplicate disk access records. RESOLUTION: vxconfigd code is modified not to create dupicate disk access records. * INCIDENT NO:2353922 TRACKING ID:2300195 SYMPTOM: Uninitialization of VxVM cdsdisk of size greater than 1 TB fails on HP-UX/ia-64 platform. DESCRIPTION: During the uninitialization of VxVM cdsdisk of size greater than 1 TB on HP- UX/ia-64 platform, DMP (dynamic-multi-pathing) paths corresponding to the GPT partitions on the VxVM cdsdisk were created incorrectly. This resulted in i/o failure while destroying the VxVM cdsdisk. RESOLUTION: This issue has been solved by performing the i/o to the whole device while uninitializing the VxVM cdsdisk. * INCIDENT NO:2360419 TRACKING ID:2237089 SYMPTOM: ======= vxrecover failed to recover the data volumes with associated cache volume. DESCRIPTION: =========== vxrecover doesn't wait till the recovery of the cache volumes is complete before triggering the recovery of the data volumes that are created on top of cache volume. Due to this the recovery might fail for the data volumes. RESOLUTION: ========== Code changes are done to serialize the recovery for different volume types. * INCIDENT NO:2360719 TRACKING ID:2359814 SYMPTOM: 1. vxconfigbackup(1M) command fails with the following error: ERROR V-5-2-3720 dgid mismatch 2. "-f" option for the vxconfigbackup(1M) is not documented in the man page. DESCRIPTION: 1. In some cases, a *.dginfo file will have two lines starting with "dgid:". It causes vxconfigbackup to fail. The output from the previous awk command returns 2 lines instead of one for the $bkdgid variable and the comparison fails, resulting in "dgid mismatch" error even when the dgids are the same. This happens in the case if the temp dginfo file is not removed during last run of vxconfigbackup, such as the script is interrupted, the temp dginfo file is updated with appending mode, vxconfigbackup.sh: echo "TIMESTAMP" >> $DGINFO_F_TEMP 2>/dev/null Therefore, there may have 2 or more dginfo are added into the dginfo file, it causes the config backup failure with dgid mismatch. 2. "-f" option to force a backup is not documented in the man page of vxconfigbackup(1M). RESOLUTION: 1. The solution is to change append mode to destroy mode. 2. Updated the vxconfigbackup(1M) man page with the "-f" option. * INCIDENT NO:2377317 TRACKING ID:2408771 SYMPTOM: VXVM does not show all the discovered devices. Number of devices shown by VXVM is lesser than those by the OS. DESCRIPTION: For every lunpath device discovered, VXVM creates a data structure and is stored in a hash table. Hash value is computed based on unique minor of the lunpath. In case minor number exceeds 831231, we encounter integer overflow and store the data structure for this path at wrong location. When we later traverse this hash list, we limit the accesses based on total number of discovered paths and as the devices with minor numbers greater than 831232 are hashed wrongly, we do not create DA records for such devices. RESOLUTION: Integer overflow problem has been resolved by appropriately typecasting the minor number and hence correct hash value is computed. * INCIDENT NO:2379034 TRACKING ID:2379029 SYMPTOM: Changing of enclosure name was not working for all devices in enclosure. All these devices were present in /etc/vx/darecs. # cat /etc/vx/darecs ibm_ds8x000_02eb auto online format=cdsdisk,privoffset=256,pubslice=2,privslice=2 ibm_ds8x000_02ec auto online format=cdsdisk,privoffset=256,pubslice=2,privslice=2 # vxdmpadm setattr enclosure ibm_ds8x000 name=new_ibm_ds8x000 # vxdisk -o alldgs list DEVICE TYPE DISK GROUP STATUS ibm_ds8x000_02eb auto:cdsdisk ibm_ds8x000_02eb mydg online ibm_ds8x000_02ec auto:cdsdisk ibm_ds8x000_02ec mydg online new_ibm_ds8x000_02eb auto - - error new_ibm_ds8x000_02ec auto - - error DESCRIPTION: /etc/vx/darecs only stores foreign devices and nopriv or simple devices, the auto device should NOT be written into this file. A DA record is flushed in the /etc/vx/darecs at the end of transaction, if R_NOSTORE flag is NOT set on a DA record. There was a bug in VM where if we initialize a disk that does not exist(e.g. using vxdisk rm) in da_list, the R_NOSTORE flag is NOT set for the new created DA record. Hence duplicate entries for these devices were created and resulted in these DAs going in error state. RESOLUTION: Source has been modified to add R_NOSTORE flag for auto type DA record created by auto_init() or auto_define(). # vxdmpadm setattr enclosure ibm_ds8x000 name=new_ibm_ds8x000 # vxdisk -o alldgs list new_ibm_ds8x000_02eb auto:cdsdisk ibm_ds8x000_02eb mydg online new_ibm_ds8x000_02ec auto:cdsdisk ibm_ds8x000_02ec mydg online * INCIDENT NO:2382705 TRACKING ID:1675599 SYMPTOM: Vxconfigd leaks memory while excluding and including a Third party Driver controlled LUN in a loop. As part of this vxconfigd loses its license information and following error is seen in system log: "License has expired or is not available for operation" DESCRIPTION: In vxconfigd code, memory allocated for various data structures related to device discovery layer is not freed which led to the memory leak. RESOLUTION: The memory is released after its scope is over. * INCIDENT NO:2382710 TRACKING ID:2139179 SYMPTOM: DG import can fail with SSB (Serial Split Brain) though the SSB does not exist. DESCRIPTION: An association between DM and DA records is done while importing any DG, if the SSB id of the DM and DA records match. On a system with stale cloned disks, the system is attempting to associate the DM with cloned DA, where the SSB id mismatch is observed and resulted in import failure with SSB mismatch. RESOLUTION: The selection of DA to associate with DM is rectified to resolve the issue. * INCIDENT NO:2382717 TRACKING ID:2197254 SYMPTOM: vxassist, the VxVM volume creation utility when creating volume with "logtype=none" doesn't function as expected. DESCRIPTION: While creating volumes on thinrclm disks, Data Change Object(DCO) version 20 log is attached to every volume by default. If the user do not want this default behavior then "logtype=none" option can be specified as a parameter to vxassist command. But with VxVM on HP 11.31 , this option does not work and DCO version 20 log is created by default. The reason for this inconsistency is that when "logtype=none" option is specified, the utility sets the flag to prevent creation of log. However, VxVM wasn't checking whether the flag is set before creating DCO log which led to this issue. RESOLUTION: This is a logical issue which is addressed by code fix. The solution is to check for this corresponding flag of "logtype=none" before creating DCO version 20 by default. * INCIDENT NO:2383705 TRACKING ID:2204752 SYMPTOM: The following message is observed after the diskgroup creation: "VxVM ERROR V-5-3-12240: GPT entries checksum mismatch" DESCRIPTION: This message is observed with the disk which was initialized as cds_efi and later on this was initialized as hpdisk. A harmless message "checksum mismatch" is thrown out even when the diskgroup initialization is successful. RESOLUTION: Remove the harmless message "GPT entries checksum mismatch" * INCIDENT NO:2384473 TRACKING ID:2064490 SYMPTOM: vxcdsconvert utility fails if disk capacity is greater than or equal to 1 TB DESCRIPTION: VxVM cdsdisk uses GPT layout if the disk capacity is greater than 1 TB and uses VTOC layout if the disk capacity is less 1 TB. Thus, vxcdsconvert utility was not able to convert to the GPT layout if the disk capacity is greater than or equal to 1 TB. RESOLUTION: This issue has been resolved by converting to proper cdsdisk layout depending on the disk capacity * INCIDENT NO:2384844 TRACKING ID:2356744 SYMPTOM: When "vxvm-recover" are executed manually, the duplicate instances of the Veritas Volume Manager(VxVM) daemons (vxattachd, vxcached, vxrelocd, vxvvrsecdgd and vxconfigbackupd) are invoked. When user tries to kill any of the daemons manually, the other instances of the daemons are left on this system. DESCRIPTION: The Veritas Volume Manager(VxVM) daemons (vxattachd, vxcached, vxrelocd, vxvvrsecdgd and vxconfigbackupd) do not have : 1. A check for duplicate instance. and 2. Mechanism to clean up the stale processes. Because of this, when user executes the startup script(vxvm-recover), all daemons are invoked again and if user kills any of the daemons manually, the other instances of the daemons are left on this system. RESOLUTION: The VxVM daemons are modified to do the "duplicate instance check" and "stale process cleanup" appropriately. * INCIDENT NO:2386763 TRACKING ID:2346470 SYMPTOM: The Dynamic Multi Pathing Administration operations such as "vxdmpadm exclude vxvm dmpnodename=" and "vxdmpadm include vxvm dmpnodename= " triggers memory leaks in the heap segment of VxVM Configuration Daemon (vxconfigd). DESCRIPTION: vxconfigd allocates chunks of memory to store VxVM specific information of the disk being included during "vxdmpadm include vxvm dmpnodename=" operation. The allocated memory is not freed while excluding the same disk from VxVM control. Also when excluding a disk from VxVM control, another chunk of memory is temporarily allocated by vxconfigd to store more details of the device being excluded. However this memory is not freed at the end of exclude operation. RESOLUTION: Memory allocated during include operation of a disk is freed during corresponding exclude operation of the disk. Also temporary memory allocated during exclude operation of a disk is freed at the end of exclude operation. * INCIDENT NO:2389095 TRACKING ID:2387993 SYMPTOM: In presence of NR (Not-Ready) devices, vxconfigd (VxVM configuration daemon) goes into disabled mode once restarted. # vxconfigd -k -x syslog # vxdctl mode mode: disabled If vxconfigd is restarted in debug mode at level 9 following message could be seen. # vxconfigd -k -x 9 -x syslog VxVM vxconfigd DEBUG V-5-1-8856 DA_RECOVER() failed, thread 87: Kernel and on-disk configurations don't match DESCRIPTION: When vxconfid is restarted, all the VxVM devices are recovered. As part of recovery the capacity of the device is read, which can fail with EIO. This error is not handled properly. As a result of this the vxconfigd is going to DISABLED state. RESOLUTION: EIO error code from read capacity ioctl is handled specifically. * INCIDENT NO:2397663 TRACKING ID:2165394 SYMPTOM: If the cloned copy of a diskgroup and a destroyed diskgroup exists on the system, an import operation imports destroyed diskgroup instread of cloned one. For example, consider a system with diskgroup dg containing disk disk1. Disk disk01 is cloned to disk02. When diskgroup dg containing disk01 is destroyed and diskgroup dg is imported, VXVM should import dg with cloned disk i.e disk02. However, it imports the diskgroup dg with disk01. DESCRIPTION: After destroying a diskgroup, if the cloned copy of the same diskgroup exists on the system, the following disk group import operation wrongly identifies the disks to be import and hence destroyed diskgroup gets imported. RESOLUTION: The diskgroup import code is modified to identify the correct diskgroup when a cloned copy of the destroyed diskgroup exists. * INCIDENT NO:2405446 TRACKING ID:2253970 SYMPTOM: Enhancement to customize private region I/O size based on maximum transfer size of underlying disk. DESCRIPTION: There are different types of Array Controllers which support data transfer sizes starting from 256K and beyond. VxVM tunable volmax_specialio controls vxconfigd's configuration I/O as well as Atomic Copy I/O size. When volmax_specialio is tuned to a value greater than 1MB to leverage maximum transfer sizes of underlying disks, import operation is failing for disks which cannot accept more than 256K I/O size. If the tunable is set to 256k then it will be the case where large transfer size of disks is not being leveraged. RESOLUTION: This enhancement leverages large disk transfer sizes as well as supports Array controllers with 256K transfer sizes. * INCIDENT NO:2408209 TRACKING ID:2291226 SYMPTOM: Data corruption can be observed on a CDS (Cross-platform Data Sharing) disk, whose capacity is more than 1 TB. The following pattern would be found in the data region of the disk. cyl alt 2 hd sec DESCRIPTION: The CDS disk maintains a SUN vtoc in the zeroth block of the disk. This VTOC maintains the disk geometry information like number of cylinders, tracks and sectors per track. These values are limited by a maximum of 65535 by design of SUN's vtoc, which limits the disk capacity to 1TB. As per SUN's requirement, few backup VTOC labels have to be maintained on the last track of the disk. VxVM 5.0 MP3 RP3 allows to setup CDS disk on a disk with capacity more than 1TB. The data region of the CDS disk would span more than 1TB utilizing all the accessible cylinders of the disk. As mentioned above, the VTOC labels would be written at zeroth block and on the last track considering the disk capacity as 1TB. The backup labels would fall in to the data region of the CDS disk causing the data corruption. RESOLUTION: Suppress writing the backup labels to prevent the data corruption. * INCIDENT NO:2409212 TRACKING ID:2316550 SYMPTOM: While doing cold/ignite install to 11.31 + VxVM 5.1, following warning messages are seen on a setup with ALUA array: "VxVM vxconfigd WARNING V-5-1-0 ddl_add_disk_instr: Turning off NMP Alua mode failed for dmpnode 0xffffffff with ret = 13 " DESCRIPTION: The above warning messages are displayed by vxconfigd started at the early boot if fails to turn off the NMP ALUA mode for a given dmp device. These messages are not harmful, as later vxconfigd started in enabled mode will turn off the NMP ALUA mode for all the dmp devices. RESOLUTION: Changes done in vxconfigd to not to print these warning messages in vxconfigd boot mode. * INCIDENT NO:2411052 TRACKING ID:2268408 SYMPTOM: 1) On suppressing the underlying path of powerpath controlled device, the disk goes in error state. 2) "vxdmpadm exclude vxvm dmpnodename=" command does not suppress TPD devices. DESCRIPTION: During discovery, H/W path corresponding to the basename is not generated for powerpath controlled devices because basename does not contain the slice portion. Device name with s2 slice is expected while generating H/W name. RESOLUTION: Whole disk name i.e., device name with s2 slice is used to generate H/W path. * INCIDENT NO:2411053 TRACKING ID:2410845 SYMPTOM: If a DG(Disk Group) is imported with reservation key, then during DG deport lots of 'reservation conflict' messages will be seen. [DATE TIME] [HOSTNAME] multipathd: VxVM26000: add path (uevent) [DATE TIME] [HOSTNAME] multipathd: VxVM26000: failed to store path info [DATE TIME] [HOSTNAME] multipathd: uevent trigger error [DATE TIME] [HOSTNAME] multipathd: VxVM26001: add path (uevent) [DATE TIME] [HOSTNAME] multipathd: VxVM26001: failed to store path info [DATE TIME] [HOSTNAME] multipathd: uevent trigger error .. [DATE TIME] [HOSTNAME] kernel: sd 2:0:0:2: reservation conflict [DATE TIME] [HOSTNAME] kernel: sd 2:0:0:2: reservation conflict [DATE TIME] [HOSTNAME] kernel: sd 2:0:0:1: reservation conflict [DATE TIME] [HOSTNAME] kernel: sd 2:0:0:2: reservation conflict [DATE TIME] [HOSTNAME] kernel: sd 2:0:0:1: reservation conflict [DATE TIME] [HOSTNAME] kernel: sd 2:0:0:2: reservation conflict DESCRIPTION: When removing a PGR(Persistent Group Reservation) key during DG deport, we need to preempt the key but the preempt operation is failed with reservation conflict error because the passing key for preemption is not correct. RESOLUTION: Code changes are made to set the correct key value for the preemption operation. * INCIDENT NO:2413908 TRACKING ID:2413904 SYMPTOM: Performing Dynamic LUN reconfiguration operations (adding and removing LUNs), can cause corruption in DMP database. This in turn may lead to vxconfigd core dump OR system panic. DESCRIPTION: When a LUN is removed from the VM using 'vxdisk rm' and at the same time some new LUN is added and in case the newly added LUN reuses the devno of the removed LUN then this may corrupt the DMP database as this condition is not handled currently. RESOLUTION: Fixed the DMP code to handle the mentioned issue. * INCIDENT NO:2415566 TRACKING ID:2369177 SYMPTOM: When using > 2TB disks and the device respons to SCSI inquiry but fails to service I/O, data corruption can occur as the write I/O would be directed at an incorrect offset DESCRIPTION: Currently when the failed I/O is retried, DMP assumes the offset to be a 32 bit value and hence I/O offsets >2TB can get truncated leading to the rety I/O issued at wrong offset value RESOLUTION: Change the offset value to a 64 bit quantity to avoid truncation during I/O retries from DMP. * INCIDENT NO:2415577 TRACKING ID:2193429 SYMPTOM: Enclosure attributes like iopolicy, recoveryoption etc do not persist across reboots in case when before vold startup itself DMP driver is already configured before with different array type (e.g. in case of root support) than stored in array.info. DESCRIPTION: When DMP driver is already configured before vold comes up (as happens in root support), then the enclosure attributes do not take effect if the enclosure name in kernel has changed from previous boot cycle. This is because when vold comes up da_attr_list will be NULL. And then it gets events from DMP kernel for data structures already present in kernel. On receiving this information, it tries to write da_attr_list into the array.info, but since da_attr_list is NULL, array.info gets overwritten with no data. And hence later vold could not correlate the enclosure attributes present in dmppolicy.info with enclosures present in array.info, so the persistent attributes could not get applied. RESOLUTION: Do not overwrite array.info of da_attr_list is NULL * INCIDENT NO:2417205 TRACKING ID:2407699 SYMPTOM: The vxassist command dumps core if the file "/etc/default/vxassist" contains the line "wantmirror=" DESCRIPTION: vxassist, the Veritas Volume Manager client utility can accept attributes from the system defaults file (/etc/default/vxassist), the user specified alternate defaults file and the command line. vxassist automatically merges all the attributes by pre-defined priority. However, a null pointer checking is missed while merging "wantmirror" attribute which leads to the core dump. RESOLUTION: Within vxassist, while merging attributes, add a check for NULL pointer. * INCIDENT NO:2421491 TRACKING ID:2396293 SYMPTOM: On VXVM rooted systems, during machine bootup, vxconfigd core dumps with following assert and machine does not bootup. Assertion failed: (0), file auto_sys.c, line 1024 05/30 01:51:25: VxVM vxconfigd ERROR V-5-1-0 IOT trap - core dumped DESCRIPTION: DMP deletes and regenerates device numbers dynamically on every boot. When we start static vxconfigd in boot mode, since ROOT file system is READ only, new DSF's for DMP nodes are not created. But, DMP configures devices in userland and kernel. So, there is mismatch in device numbers of the DSF's and that in DMP kernel, as there are stale DSF's from previous boot present. This leads vxconfigd to actually send I/O's to wrong device numbers resulting in claiming disk with wrong format. RESOLUTION: Issue is fixed by getting the device numbers from vxconfigd and not doing stat on DMP DSF's. * INCIDENT NO:2428179 TRACKING ID:2425722 SYMPTOM: VxVM's subdisk operation - vxsd mv - fails on subdisk sizes greater than or equal to 2TB. Eg: #vxsd -g nbuapp mv disk_1-03 disk_2-03 VxVM vxsd ERROR V-5-1-740 New subdisks have different size than subdisk disk_1- 03, use -o force DESCRIPTION: VxVM code uses 32-bit unsigned integer variable to store the size of subdisks which can only accommodate values less than 2TB. Thus, for larger subdisk sizes integer overflows resulting in the subdisk move operation failure. RESOLUTION: The code has been modified to accommodate larger subdisk sizes. * INCIDENT NO:2440351 TRACKING ID:2440349 SYMPTOM: The grow operation on a DCO volume may grow it into any 'site' not honoring the allocation requirements strictly. DESCRIPTION: When a DCO volume is grown, it may not honor the allocation specification strictly to use only a particular site even though they are specified explicitly. RESOLUTION: The Data Change Object of Volume Manager is modified such that it will honor the alloc specification strictly if provided explicitly * INCIDENT NO:2442850 TRACKING ID:2317703 SYMPTOM: When the vxesd daemon is invoked by device attach & removal operations in a loop, it leaves open file descriptors with vxconfigd daemon DESCRIPTION: The issue is caused due to multiple vxesd daemon threads trying to establish contact with vxconfigd daemon at the same time and ending up using losing track of the file descriptor through which the communication channel was established RESOLUTION: The fix for this issue is to maintain a single file descriptor that has a thread safe reference counter thereby not having multiple communication channels established between vxesd and vxconfigd by various threads of vxesd. * INCIDENT NO:2477291 TRACKING ID:2428631 SYMPTOM: Shared DG import or Node Join fails with Hitachi Tagmastore storage DESCRIPTION: CVM uses different fence key for every DG. The key format is of type 'NPGRSSSS' where N is the node id (A,B,C..) and 'SSSS' is the sequence number. Some arrays have a restriction on total number of unique keys that can be registered (eg Hitachi Tagmastore) and hence causes issues for configs involving large number of DGs, rather the product of #DGs and #nodes in the cluster. RESOLUTION: Having a unique key for each DG is not essential. Hence a tunable is added to control this behavior. # vxdefault list KEYWORD CURRENT-VALUE DEFAULT-VALUE ... same_key_for_alldgs off off ... Default value of the tunable is 'off' to preserve the current behavior. If a configuration hits the storage array limit on total number of unique keys, the tunable value could be changed to 'on'. # vxdefault set same_key_for_alldgs on # vxdefault list KEYWORD CURRENT-VALUE DEFAULT-VALUE ... same_key_for_alldgs on off ... This would make CVM generate same key for all subsequent DG imports/creates. Already imported DGs need to be deported and re-imported for them to take into consideration the changed value of the tunable. * INCIDENT NO:2480006 TRACKING ID:2400654 SYMPTOM: "vxdmpadm listenclosure" command hangs because of duplicate enclosure entries in /etc/vx/array.info file. Example: Enclosure "emc_clariion0" has two entries. #cat /etc/vx/array.info DD4VM1S emc_clariion0 0 EMC_CLARiiON DISKS disk 0 Disk DD3VM2S emc_clariion0 0 EMC_CLARiiON DESCRIPTION: When "vxdmpadm listenclosure" command is run, vxconfigd reads its in-core enclosure list which is populated from the /etc/vx/array.info file. Since the enclosure "emc_clariion0" (as mentioned in the example) is also a last entry within the file, the command expects vxconfigd to return the enclosure information at the last index of the enclosure list. However because of duplicate enclosure entries,vxconfigd returns a different enclosure information thereby leading to the hang. RESOLUTION: The code changes are made in vxconfigd to detect duplicate entries in /etc/vx/array.info file and return the appropriate enclosure information as requested by the vxdmpadm command. * INCIDENT NO:2483476 TRACKING ID:2491091 SYMPTOM: The vxdisksetup(1M) command fails on the disk which have stale EFI information, with the following error: VxVM vxdisksetup ERROR V-5-2-4686 Disk is currently an EFI formatted disk. Use -f option to force EFI removal. DESCRIPTION: The vxdisksetup(1M) command checks for the EFI headers on the disk, if found then vxdisksetup(1M) command exits with the suggestion to use "-f" option. The check for the EFI headers is not correct to take care of stale EFI headers, so the vxdisksetup(1M) command exits with the error. RESOLUTION: The code is modified to check the valid EFI headers. * INCIDENT NO:2485230 TRACKING ID:2481938 SYMPTOM: The vxdisk command displays incorrect pubpath of an EFI partitioned disk on HP 1131 platform. For example, # vxdisk list cXtXdXs2 Device: diskX_p2 devicetag: cXtXdXs2 .. pubpaths: block=/dev/vx/dmp/cXtXdX char=/dev/vx/rdmp/cXtXdX ... DESCRIPTION: The VxVM configuration daemon (vxconfigd) maintains all the disks' information. On HP platform, an EFI disk has EFI_SDI_FLAG flag set. When the vxconfigd sets up an EFI partitioned disk, the EFI_SDI_FLAG is checked firstly and vxconfigd changes the disk access name according to the flag and the disk's original value. However, in some cases vxconfigd still uses the original disk access name not the new disk access name which lead to the incorrect subpath value. RESOLUTION: vxconfigd is modified to use the new disk access name. * INCIDENT NO:2485278 TRACKING ID:2386120 SYMPTOM: Error messages printed in the syslog in the event of master takeover failure in some situations are not be enough to find out the root cause of the failure. DESCRIPTION: During master takeover if the new master encounters some errors, the master takeover operation fails. We have messages in the code to log the reasons for the failure. These log messages are not available on the customer setups. These are generally enabled in the internal development\testing scenarios. RESOLUTION: Some of the relevant messages have been modified such that they will now be available on the customer setups as well, logging crucial information for root cause analysis of the issue. * INCIDENT NO:2485288 TRACKING ID:2431470 SYMPTOM: 1. "vxpfto" command sets PFTO(Powerfail Timeout) value on a wrong VxVM device when it passes DM(Disk Media) name to the "vxdisk set" command with -g option. 2. "vxdisk set" command does not work when DA name is specified either -g option specified or not. Ex.) # vxdisk set [DA name] clone=off VxVM vxdisk ERROR V-5-1-5455 Operation requires a disk group # vxdisk -g [DG name] set [DA name] clone=off VxVM vxdisk ERROR V-5-1-0 Device [Da name] not in configuration or associated with DG [DG name] DESCRIPTION: 1. "vxpfto" command invokes "vxdisk set" command to set the PFTO value. It shall accept both DM and DA names for device specification. However DM and DA names can have conflicts such that even within the same disk group, the same name can refer to different devices - one as a DA name and another as a DM name. "vxpfto" command uses a DM name with -g option when invoking the "vxdisk set" command but it will choose a matching DA name before a DM name. This causes incorrect device to be acted upon. Both DM and DA name can be specified for the "vxdisk set" command with -g option however the DM name are given preference with -g option from the design perspective. 2. "vxdisk set" command shall accept DA name for device specification. Without -g option, the command shall work only when DA name is specified. However it doesn't work because the disk group name is not extracted from the DA record correctly. Hence the first error. With -g option the DA name specified is treated as a matching DM name wrongly, hence the second error. RESOLUTION: Code changes are made to make the "vxdisk set" command working correctly on DA name without -g option and on both DM and DA names with -g option. The given preference is DM name when -g option is specified. It resolves the "vxpfto" command issue as well. * INCIDENT NO:2492016 TRACKING ID:2232411 SYMPTOM: Subsequent resize operations of raid5 or layered volumes may fail with "VxVM vxassist ERROR V-5-1-16092 Volume TCv7-13263: There are other recovery activities. Cannot grow volume" DESCRIPTION: If a user tries to grow or shrink a raid5 volume or a layered volume more than once using vxassist command, the command may fail with the above mentioned error message. RESOLUTION: 1. Skip setting recover offset for RAID volumes. 2. For layered volumes, topvol: skip setting recover offset. subvols: handles separately later. (code exists). INCIDENTS FROM OLD PATCHES: --------------------------- NONE