Veritas InfoScale™ 7.4.2 Release Notes - Solaris
- Introduction
- Requirements
- Changes introduced in 7.4.2
- Fixed issues
- 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
- Veritas cluster configuration wizard limitations
- Limitations related to the VCS database agents
- Cluster Manager (Java console) limitations
- Limitations related to LLT
- 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 software limitations
- Known issues
- Issues related to installation and upgrade
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- Veritas Volume Manager 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
- 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
- Issues related to installation and upgrade
Mount command may fail to mount the file system (3913246)
For a file system that was earlier mounted on cluster nodes the first Mount command may fail with the following error:
UX:vxfs mount.vxfs: ERROR: V-3-28543: Cannot be mounted until it has been cleaned by fsck. Please run "fsck -t vxfs -y /dev/vx/rdsk/<DiskGroup_Name>/<Volume_Name>" before mounting. Please refer to fsck_vxfs man page for details.
At the same time, the following error message may appear in the system log:
vxfs: msgcnt 463 mesg 021: V-2-21: vx_fs_init - /dev/vx/dsk/<DiskGroup_Name>/<Volume_Name> file system validation failure.
These are generic messages and the Mount command may fail due to multiple reasons.
Workaround:
Verify all the per node logs to check for a dirty log, if any.
Mount the file system with delayfsck mount option.
Notes:
This workaround is applicable only if a dirty log is found.
Step 2 is applicable only for disk layout version 11 or later. For disk layout version prior to 11, you must run the Full fsck command before the file system is mounted.
Even if you have mounted the file system with delayfsck mount option, you must run the Full fsck command at a later point in time. You may plan the application downtime and then run the Full fsck command.