README VERSION : 1.1 README CREATION DATE : 2015-12-09 PATCH ID : 7.0.1.000 PATCH NAME : VRTSvxfs 7.0.1.000 BASE PACKAGE NAME : VRTSvxfs BASE PACKAGE VERSION : 7.0.0.000 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : aix61,aix71 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : HANG , PANIC PATCH CRITICALITY : CRITICAL HAS KERNEL COMPONENT : YES ID : NONE REBOOT REQUIRED : YES REQUIRE APPLICATION DOWNTIME : Yes PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer to Install guide for install instructions PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to Install guide for uninstall instructions SPECIAL INSTRUCTIONS: ---------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:7.0.1.000 3844377 (2806466) A reclaim operation on a file system that is mounted on a Logical Volume Manager (LVM) may panic the system. 3844417 (3762125) Directory size increases abnormally. 3844429 (3762174) fsfreeze and vxdump commands may not work together. 3844435 (3808033) When using 6.2.1 ODM on RHEL7, Oracle resource cannot be killed after forced umount via VCS. 3844442 (3662284) File Change Log (FCL) read may retrun ENXIO. 3844444 (3735697) vxrepquota reports error 3845203 (3695367) Unable to remove volume from multi-volume VxFS using "fsvoladm" command. 3847324 (3526845) The Data Translation Lookaside Buffer (DTLB) panic may occur when the directory entries are read. 3847425 (3827491) Data relocation is not executed correctly if the IOTEMP policy is set to AVERAGE. 3849315 (3764824) Internal Cluster File System (CFS) test hits debug assert. 3849331 (3729158) Deadlock occurs due to incorrect locking order between write advise and dalloc flusher thread. 3849339 (3761603) Internal assert failure because of invalid extop processing at the mount time. 3852546 (3807366) The man pages included in the VRTSvxfs, VRTSfsadv and VRTSfssdk packages have an incorrect product version. 3854520 (3857254) Assert failure because of missed flush before taking filesnap of the file. 3855265 (3859230) Module information shows wrong VxFS module version. 3857831 (3811849) System panics while executing lookup() in a directory with large directory hash(LDH). 3857998 (3857444) The default permission of /etc/vx/vxfssystem file is incorrect. SUMMARY OF KNOWN ISSUES: ----------------------------------------- 3844449 (3833816) [VxFS][09140252][Axway Inc]VxFS/CFS coherency issue 3847329 (1428611) [VxFS][09035216][Discovery Health (Pty) Ltd] FS commands hang on both nodes of CFS cluster. 3855046 (3855045) L10N:JP File missing for commands . There is no man-page for command . 3855105 (3643800) [7.0.1][AxRT][LM][Conformance][fscache] test having multiple failures. KNOWN ISSUES : -------------- * INCIDENT NO:3844449 TRACKING ID:3833816 SYMPTOM: In a CFS cluster, one node may return stale data. WORKAROUND: No * INCIDENT NO:3847329 TRACKING ID:1428611 SYMPTOM: 'vxcompress' can spew many GLM block lock messages over the LLT network. WORKAROUND: No * INCIDENT NO:3855046 TRACKING ID:3855045 SYMPTOM: Man pages of some VxFS Command for JPN language are missing. WORKAROUND: No * INCIDENT NO:3855105 TRACKING ID:3643800 SYMPTOM: On the online cache device you should not perform the mkfs operation, because any subsequent fscache operation panics WORKAROUND: Workaround is not available. FIXED INCIDENTS: PATCH ID:7.0.1.000 * INCIDENT NO:3844377 TRACKING ID:2806466 SYMPTOM: A reclaim operation on a file system that is mounted on an LVM volume using the fsadm(1M) command with the -R option may panic the system. And the following stack trace is displayed: vx_dev_strategy+0xc0() vx_dummy_fsvm_strategy+0x30() vx_ts_reclaim+0x2c0() vx_aioctl_common+0xfd0() vx_aioctl+0x2d0() vx_ioctl+0x180() DESCRIPTION: Thin reclamation supports only mounted file systems on a VxVM volume. RESOLUTION: The code is modified to return errors without panicking the system if the underlying volume is LVM. * INCIDENT NO:3844417 TRACKING ID:3762125 SYMPTOM: Directory size sometimes keeps increasing even though the number of files inside it doesn't increase. DESCRIPTION: This only happens to CFS. A variable in the directory inode structure marks the start of directory free space. But when the directory ownership changes, the variable may become stale, which could cause this issue. RESOLUTION: The code is modified to reset this free space marking variable when there's ownershipchange. Now the space search goes from beginning of the directory inode. * INCIDENT NO:3844429 TRACKING ID:3762174 SYMPTOM: When fsfreeze is used together with vxdump, the fsfreeze command gets timeout and vxdump command fails. DESCRIPTION: The vxdump command may try to read mount list file to get information of the corresponding mount points. This behavior results in taking a file system active level, in order to synchronize with file system reinit. But in case of fsfreeze, taking the active level will never succeed, since the file system is already freezed, so this causes a deadlock and finally results in the fsfreeze timeout. RESOLUTION: Don't use fsfreeze and vxdump command together. * INCIDENT NO:3844435 TRACKING ID:3808033 SYMPTOM: After a service group is set offline via VOM or VCSOracle process is left in an unkillable state. DESCRIPTION: Whenever ODM issues an async request to FDD, FDD is required to do iodone processing on it, regardless of how far the request gets. The forced unmount causes FDD to take one of the early error branch which misses iodone routine for this particular async request. From ODM's perspective, the request is submitted, but iodone will never be called. This has several bad consequences, one of which is a user thread is blocked uninterruptibly forever, if it waits for request. RESOLUTION: The code is modified to add iodone routine in the error handling code. * INCIDENT NO:3844442 TRACKING ID:3662284 SYMPTOM: File Change Log (FCL) read may retrun ENXIO as follows: # file changelog changelog: ERROR: cannot read `changelog' (No such device or address) DESCRIPTION: VxFS reads FCL file and returns ENXIO when there is a HOLE in the file. RESOLUTION: The code is modified to zero out the user buffer when hitting a hole if FCL read is from user space. * INCIDENT NO:3844444 TRACKING ID:3735697 SYMPTOM: vxrepquota reports error like, # vxrepquota -u /vx/fs1 UX:vxfs vxrepquota: ERROR: V-3-20002: Cannot access /dev/vx/dsk/sfsdg/fs1:ckpt1: No such file or directory UX:vxfs vxrepquota: ERROR: V-3-24996: Unable to get disk layout version DESCRIPTION: vxrepquota checks each mount point entry in mounted file system table. If any checkpoint mount point entry presents before the mount point specified in the vxrepquota command, vxrepquota will report errors, but the command can succeed. RESOLUTION: Skip checkpoint mount point in the mounted file system table. * INCIDENT NO:3845203 TRACKING ID:3695367 SYMPTOM: Unable to remove volume from multi-volume VxFS using "fsvoladm" command. It fails with "Invalid argument" error. DESCRIPTION: Volumes are not being added in the in-core volume list structure correctly. Therefore while removing volume from multi-volume VxFS using "fsvoladm", command fails. RESOLUTION: The code is modified to add volumes in the in-core volume list structure correctly. * INCIDENT NO:3847324 TRACKING ID:3526845 SYMPTOM: The Data Translation Lookaside Buffer (DTLB) panic may occur when the directory entries are read. The following stack trace is observed: bcmp() vx_real_readdir3() vx_readdir3() getdents() syscall() DESCRIPTION: When the directory entry is read, the directory name is checked using the bcmp () function against the VX_PDMAGIC identifier string. This is used to determine if the directory is the partitioned directory or not. The thread panics in the vx_real_readdir3() function, because the length of the directory name is less than the length of the VX_PDMAGIC identifier string. As a result, the bcmp() function accesses the unallocated area. RESOLUTION: The code is modified to check if the length of the directory-entry name is greater thanthe VX_PDMAGIC string, before the bcmp() function is called. * INCIDENT NO:3847425 TRACKING ID:3827491 SYMPTOM: Data relocation is not executed correctly if the IOTEMP policy is set to AVERAGE. DESCRIPTION: Database table is not created correctly which results in an error on the database query. This affects the relocation policy of data and the files are not relocated properly. RESOLUTION: The code is modified fix the database table creation issue. Therelocation policy based calculations are done correctly. * INCIDENT NO:3849315 TRACKING ID:3764824 SYMPTOM: Internal Cluster File System (CFS) test hits debug assert DESCRIPTION: Internal debug assert is seen if GLM (Group Lock Manager) is recovering at the same time with secondary nodes mount, specifically when GLM recovery happens between attaching a file system and mounting file system. RESOLUTION: The code is modified to handle GLM reconfiguration issue. * INCIDENT NO:3849331 TRACKING ID:3729158 SYMPTOM: The fuser and other commands hang on VxFS file systems. DESCRIPTION: The hang is seen while 2 threads contest for 2 locks -ILOCK and PLOCK. The writeadvise thread owns the ILOCK but is waiting for the PLOCK, while the dalloc thread owns the PLOCK and is waiting for the ILOCK. RESOLUTION: The code is modified to correct the order of locking. Now PLOCK is followed by ILOCK. * INCIDENT NO:3849339 TRACKING ID:3761603 SYMPTOM: Full fsck flag is set incorrectly at the mount time. DESCRIPTION: Its possible that extop processing is deferred during umount (i.e. in case of crash or disk failure) and kept on disk, so that mount can process them. During mount, inode can have multiple extop set. If inode has trim and reorg extop set during mount, fullfsck flag is set incorrectly. RESOLUTION: The code is modified to avoid such unnecessary setting of fullfsck. * INCIDENT NO:3852546 TRACKING ID:3807366 SYMPTOM: The man pages included in the VRTSvxfs, VRTSfsadv and VRTSfssdk packages identify the product version incorrectly as 6.2, instead of the correct 7.0. DESCRIPTION: Man pages included in the packages identify the product version they document. For the man pages included in the 7.0 release, this version is incorrectly mentioned as 6.2. The online versions of the man pages available from SORT have previously been updated to mention the correct version. RESOLUTION: The versions in the man pages have been corrected and the updated man pages have been included in the packages. * INCIDENT NO:3854520 TRACKING ID:3857254 SYMPTOM: Assert failure because of missed flush before taking filesnap of the file. DESCRIPTION: If the delayed extended write on the file is not completed but the snap of the file is taken, then the inode size is not updated correctly. This will trigger internal assert because of incorrect inode size. RESOLUTION: The code is modified to flush the delayed extended write before taking filesnap. * INCIDENT NO:3855265 TRACKING ID:3859230 SYMPTOM: Module information shows wrong VxFS module version. DESCRIPTION: Module information shows wrong VxFS module version. RESOLUTION: The code is modified to correctly show VxFS module version for 7.0.1 * INCIDENT NO:3857831 TRACKING ID:3811849 SYMPTOM: System panics due to size mismatch in the cluster-wide buffers containing hash bucket data. Offending stack looks like below: $cold_vm_hndlr bubbledown as_ubcopy vx_populate_bpdata vx_getblk_clust $cold_vx_getblk vx_exh_getblk vx_exh_get_bucket vx_exh_lookup vx_dexh_lookup vx_dirscan vx_dirlook vx_pd_lookup vx_lookup_pd vx_lookup lookupname lstat syscall On some platforms, instead of panic, LDH corruption can be reported. Full fsck can report some meta-data inconsistencies, which looks like the below sample messages: fileset 999 primary-ilist inode 263 has invalid alternate directory index (fileset 999 attribute-ilist inode 8193), clear index? (ynq)y fileset 999 primary-ilist inode 29879 has invalid alternate directory index (fileset 999 attribute-ilist inode 8194), clear index? (ynq)y fileset 999 primary-ilist inode 1070691 has invalid alternate directory index (fileset 999 attribute-ilist inode 24582), clear index? (ynq)y fileset 999 primary-ilist inode 1262102 has invalid alternate directory index (fileset 999 attribute-ilist inode 8198), clear index? (ynq)y DESCRIPTION: On a very fragmented file system with FS block sizes 1K, 2K or 4K, any segment of the hash inode (i.e. buckets/CDF/directory segment with fixed size: 8K) can spread across multiple extents. Instead of initializing the buffers on the final bmap after all allocations are finished, LDH code allocates the buffer-cache buffers as the allocations come along.As a result, small allocations can be merged in final bmap, e.g. two CFS nodes can end up having buffers representing same metadata, with different sizes. This leads to panics because the buffers are passed around the cluster or the corruption reaches LDH portions on the disk. RESOLUTION: The code is modified to separate the allocation and buffer initialization in LDH code paths. * INCIDENT NO:3857998 TRACKING ID:3857444 SYMPTOM: The default permission of /etc/vx/vxfssystem file is incorrect. DESCRIPTION: When creating the file "/etc/vx/vxfssystem", no permission is passed, which results in having the permission to this file as 000. RESOLUTION: The code is modified to create the file "/etc/vx/vxfssystem" with default permission as "600". INCIDENTS FROM OLD PATCHES: --------------------------- NONE