3.3. Red Hat Storage and Red Hat Enterprise Virtualization Integration

In the case that the Red Hat Storage server nodes and the Red Hat Enterprise Virtualization Hypervisors are present in the same data center, the servers of both types are listed for selection when you create a virtual machine or add a storage domain. Red Hat recommends that you create a separate data center for the Red Hat Storage server nodes.

BZ# 867236

While deleting a virtual machine using the Red Hat Enterprise Virtualization Manager, the virtual machine is deleted but remains in the actual storage. This consumes unnecessary storage.

Workaround: Delete the virtual machine manually using the command line interface. Deleting the virtual image file frees the space.

BZ# 918032

In this release, the direct-io-mode=enable mount option does not work on the Hypervisor.

BZ# 979901

Virtual machines may experience very slow performance when a rebalance operation is initiated on the storage volume. This scenario is observed when the load on storage servers are extremely high. Hence, it is recommended to run the rebalance operation when the load is low.

BZ# 856121

When a volume starts, a .glusterfs directory is created in the back-end export directory. When a remove-brick command is performed, it only changes the volume configuration to remove the brick and stale data is present in back-end export directory.

Workaround: Run this command on the Red Hat Storage Server node to delete the stale data.

rm -rf /export-dir

# rm -rf /export-dir

BZ# 866908

The gluster volume heal VOLNAME info command gives stale entries in its output in a few scenarios.

Workaround: Execute the command after 10 minutes. This removes the entries from internal data structures and the command does not display stale entries.