Veritas InfoScale™ 7.0.1 Release Notes - Linux
- Important release information
- About the Veritas InfoScale product suite
- Licensing Veritas InfoScale Availability
- About Veritas Services and Operations Readiness Tools
- Changes introduced in 7.0.1
- Licensing changes for InfoScale 7.0.1
- Changes to Dynamic Multi-Pathing in this release
- Changes to InfoScale Availability in this release
- Not supported in this release
- System requirements
- Fixed Issues
- Known Issues
- Issues related to installation and upgrade
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- Veritas Volume Manager known issues
- Virtualization known issues
- Veritas File System known issues
- Replication known issues
- Cluster Server known issues
- Operational issues for VCS
- Issues related to the VCS engine
- Issues related to the bundled agents
- Issues related to the VCS database agents
- Issues related to the agent framework
- Cluster Server agents for Volume Replicator known issues
- Issues related to Intelligent Monitoring Framework (IMF)
- Issues related to global clusters
- Issues related to the Cluster Manager (Java Console)
- VCS Cluster Configuration wizard issues
- LLT known issues
- I/O fencing known issues
- GAB known issues
- Operational issues for VCS
- Storage Foundation and High Availability known issues
- Storage Foundation Cluster File System High Availability known issues
- Storage Foundation for Oracle RAC known issues
- Oracle RAC known issues
- Storage Foundation Oracle RAC issues
- Storage Foundation for Databases (SFDB) tools known issues
- Storage Foundation for Sybase ASE CE known issues
- Issues related to installation and upgrade
- Software Limitations
- Virtualization software limitations
- Storage Foundation software limitations
- Dynamic Multi-Pathing software limitations
- Veritas Volume Manager software limitations
- Veritas File System software limitations
- SmartIO software limitations
- Replication software limitations
- Cluster Server software limitations
- Limitations related to bundled agents
- Limitations related to VCS engine
- Cluster configuration wizard limitations
- Limitations related to the VCS database agents
- Cluster Manager (Java console) limitations
- Limitations related to I/O fencing
- Limitations related to bundled agents
- Storage Foundation Cluster File System High Availability software limitations
- Storage Foundation for Oracle RAC software limitations
- Storage Foundation for Databases (SFDB) tools software limitations
- Storage Foundation for Sybase ASE CE software limitations
- Documentation
Veritas File System fixed issues in 7.0.1
Table: Veritas File System (VxFS) fixed issues in 7.0.1 lists the incidents that are fixed in Veritas File System (VxFS) in 7.0.1.
Table: Veritas File System (VxFS) fixed issues in 7.0.1
Incident | Description |
---|---|
3859644 | The Openssl 1.0.1p needs libssl.so.1.0.0 and libcrypto.so.1.0.0 libraries. |
3859642 | The PDDE SDK needs to be updated for OpenSSL 1.0.1p. |
3857444 | The default permission of /etc/vx/vxfssystem file is incorrect. |
3857254 | Assert failure because of missed flush before taking filesnap of the file. |
3854421 | The library libpq is not required in latest PDDE. |
3853338 | Files on VxFS are corrupted while running the sequential asynchronous write workload under high memory pressure. |
3633683 | VxFS thread consumes high CPU while running an application that makes excessive sync() calls. |
3827491 | Data relocation is not executed correctly if the IOTEMP policy is set to AVERAGE. |
3821700 | GMS module failed to load on SLES11 SP4. |
3821698 | GLM module fails to get loaded on SLES11 SP4. |
3821693 | ODM module fails to get loaded on SLES11 SP4. |
3821686 | VxFS module fails to get loaded on SLES11 SP4. |
3812914 | ONE_LINE_ABSTRACT:On RHEL 6.5 and RHEL 6.4 latest kernel patch, umount(8) system call hangs if anapplication watches for inode events using inotify(7) APIs. |
3811849 | System panics while executing lookup() in a directory with large directory hash(LDH). |
3808033 | When using 6.2.1 ODM on RHEL7, Oracle resource cannot be killed after forced umount via VCS. |
3807367 | The man pages included in the VRTScavf package have an incorrect product version. |
3807366 | The man pages included in the VRTSvxfs, VRTSfsadv and VRTSfssdk packages have an incorrect product version. |
3804400 | /opt/VRTS/bin/cp does not return any error when quota hard limit is reached and partial write is encountered. |
3801320 | Core dump is generated when deduplication is running. |
3765928 | "cfsshare config -p all" doesn't populating smb.conf(sambaconfiguration file) properly for some global variables. |
3765921 | On RHEL7 onwards, Pluggable Authentication Modules (PAM) related error messages for Samba daemon may be observed in system logs after adding CIFS (common internet file system) share. |
3764824 | Internal Cluster File System (CFS) test hits debug assert. |
3762174 | fsfreeze and vxdump commands may not work together. |
3762125 | Directory size increases abnormally. |
3761603 | Internal assert failure because of invalid extop processing at the mount time. |
3759886 | In case of nested mount, force umount of parent leaves stale child entry in /etc/mtab even after subsequent umount of child. |
3758102 | In Cluster File System(CFS) on Linux, stack overflow occurs when ODM file is created. |
3736398 | NULL pointer dereference panic in lazy unmount. |
3735697 | "vxrepquota" reports error. |
3731844 | ONE_LINE_ABSTRACT:umount -r option fails for vxfs 6.2. |
3729158 | Deadlock occurs due to incorrect locking order between write advise and dalloc flusher thread. |
3712961 | Stack overflow is detected in vx_dio_physio() right after submitting the I/O. |
3708836 | fallocate causes data corruption. |
3695367 | Unable to remove volume from multi-volume VxFS using "fsvoladm" command. |
3689354 | Users having write permission on file cannot open the file with O_TRUNC if the file has setuid or setgid bit set. |
3662284 | ONE_LINE_ABSTRACT:File Change Log (FCL) read may retrun ENXIO. |
3526845 | The Data Translation Lookaside Buffer (DTLB) panic may occur when the directoryentries are read. |
3253210 | The file system hangs when it reaches the space limitation. |
2806466 | A reclaim operation on a file system that is mounted on aLogical Volume Manager (LVM) may panic the system. |