Veritas Cluster Server Release Notes
Veritas⢠Cluster Server Release Notes: Linux - SORT - Symantec
Veritas⢠Cluster Server Release Notes: Linux - SORT - Symantec
- No tags were found...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Veritas</strong> <strong>Cluster</strong> <strong>Server</strong> <strong>Release</strong> <strong>Notes</strong><br />
Software limitations<br />
79<br />
■<br />
■<br />
ext4 filesystem configured on VxVM<br />
xfs filesystem configured on VxVM<br />
Share agent limitations<br />
Limitations related to IMF<br />
To ensure proper monitoring by the Share agent, verify that the /var/lib/nfs/etab<br />
file is clear upon system reboot. Clients in the Share agent must be specified as<br />
fully qualified host names to ensure seamless failover.<br />
Driver requirements for DiskReservation agent<br />
The VRTSvcsdr package ships the scsiutil utility. DiskReservation agent supports<br />
only those drivers supported by the scsiutil utility.<br />
Volumes in a disk group start automatically irrespective of the<br />
value of the StartVolumes attribute in VCS<br />
Volumes in a disk group are started automatically when the disk group is imported,<br />
irrespective of the value of the StartVolumes attribute in VCS. This behavior is<br />
observed if the value of the system-level attribute autostartvolumes in <strong>Veritas</strong><br />
Volume Manager is set to On.<br />
Workaround: If you do not want the volumes in a disk group to start automatically<br />
after the import of a disk group, set the autostartvolumes attribute to Off at the<br />
system level.<br />
Application agent limitations<br />
■<br />
■<br />
■<br />
ProPCV fails to prevent execution of script-based processes configured under<br />
MonitorProcesses.<br />
IMF registration on Linux for “bind” file system type is not supported.<br />
In case of SLES11 SP1 and RHEL6.1:<br />
■<br />
■<br />
IMF should not be enabled for the resources where the BlockDevice can get<br />
mounted on multiple MountPoints.<br />
If FSType attribute value is nfs, then IMF registration for “nfs” file system<br />
type is not supported.