This update also fixes numerous bugs and adds various enhancements. Spaceprecludes documenting all of these changes in this advisory. Users aredirected to the Red Hat Gluster Storage 3.1 Technical Notes, linked to inthe References section, for information on the most significant of thesechanges.

This advisory introduces the following new features:

Writable SnapshotsRed Hat Gluster Storage snapshots can now be cloned and made writable by creating a new volume based on an existing snapshot. Clones are space efficient, as the cloned volume and original snapshot share the same logical volume back end, only consuming additional space as the clone diverges from the snapshot. For more information, see the Red Hat Gluster Storage 3.1 Administration Guide: https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/.

Red Hat Gluster Storage for ContainersWith the Red Hat Gluster Storage 3.1 update 2 release a Red Hat Gluster Storage environment can be set up in a container. Containers use shared operating systems and are much more efficient than hypervisors in system resource terms. Containers rest on top of a single Linux instance and allows applications to use the same Linux kernel as the system that they're running on. This improves the overall efficiency and reduces the space consumption considerably. For more information, see the Red Hat Gluster Storage 3.1 Administration Guide: https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/.

Samba Asynchronous I/OWith this release, asynchronous I/O from Samba to Red Hat Gluster Storage is supported. The aio read size option is now enabled and set to 4096 by default. This increases the throughput when the client is multithreaded or there are multiple programs accessing the same share. If you have Linux clients using SMB 2.0 or higher, Red Hat recommends disabling asynchronous I/O (setting aio read size to 0).

All users of Red Hat Gluster Storage are advised to apply this update.

Solution

Before applying this update, make sure all previously released erratarelevant to your system have been applied.