17.08.2015 Views

Veritas Cluster Server Release Notes

Veritas™ Cluster Server Release Notes: Linux - SORT - Symantec

Veritas™ Cluster Server Release Notes: Linux - SORT - Symantec

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Veritas</strong> <strong>Cluster</strong> <strong>Server</strong> <strong>Release</strong> <strong>Notes</strong><br />

Known issues<br />

48<br />

Concurrency violation observed during migration of monitored<br />

virtual machine [2755936]<br />

If a VCS service group has more than one KVMGuest resource monitoring virtual<br />

machine and one of the virtual machines is migrated to another host, a service<br />

group level concurrency violation occurs as the service group state goes into<br />

PARTIAL state on multiple nodes.<br />

Workaround: Configure only one KVMGuest resource in a Service group.<br />

LVM logical volume may get stuck with reiserfs file system on<br />

SLES11 [2120133]<br />

LVM logical volume may get stuck with reiserfs file system on SLES11 if the service<br />

group containing the logical volume is switched continuously between the cluster<br />

node.<br />

This issue may be observed:<br />

■<br />

■<br />

■<br />

During the continuous switching of the service group having the LVM logical<br />

volume with reiserfs file system.<br />

On SLES11 and with reiserfs file system only.<br />

Due to the behavior of device-mapper on SLES11.<br />

However, the issue is not consistent. Sometimes, the device-mapper gets stuck<br />

while handling the logical volumes and causes the logical volume to hang. In such<br />

a case, LVM2 commands also fail to clear the logical volume. VCS cannot handle<br />

this situation as the LVM2 commands are unable to deactivate the hung logical<br />

volume.<br />

Resolution: You must restart the system on which the logical volumes are stuck in<br />

this situation.<br />

KVMGuest resource comes online on failover target node when<br />

started manually [2394048]<br />

The VCS KVMGuest resource comes online on failover target node when VM guest<br />

started manually, even though the resource is online on the primary node.<br />

Red Hat kernel-based virtual machine (KVM) allows you to start the guest using<br />

same guest image on multiple nodes. The guest image is residing on the cluster<br />

file system. If the guest image is stored on the cluster file system, then it becomes<br />

available on all the cluster nodes simultaneously.<br />

If the KVMGuest resource of VCS has made the guest online on one node by<br />

starting it using the guest image on cluster file system and if you manually start the<br />

same guest on the other node, Red Hat KVM does not prevent you from doing so.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!