Chapter 8. Updating to Red Hat Gluster Storage 3.1.x


Updating from Red Hat Enterprise Linux 6 based Red Hat Gluster Storage to Red Hat Enterprise Linux 7 based Red Hat Gluster Storage is not supported.


In Red Hat Enterprise Linux 7 based Red Hat Gluster Storage, updating to Red Hat Gluster Storage 3.1.x will reload firewall rules. All the runtime-only changes done until the reload, if it was not included in the permanent configuration, will be lost.
A software update is a minor release that includes bug fixes for features, software enhancements etc. Red Hat strongly recommends you update your Red Hat Gluster Storage software regularly with the latest security patches and upgrades. Associate your system with a content server to update existing content or to install new content. This ensures that your system is up-to-date with security updates and upgrade
To keep your Red Hat Gluster Storage system up-to-date, associate the system with the RHN or your locally-managed content service. This ensures your system automatically stays up-to-date with security patches and bug fixes.


  • Asynchronous errata update releases of Red Hat Gluster Storage include all fixes that were released asynchronously since the last release as a cumulative update.
  • When there are large number of snapshots, ensure to deactivate the snapshots before performing an update. The snapshots can be activated after the update is complete. For more information, see Chapter 4.1 Starting and Stopping the glusterd service in the Red Hat Gluster Storage 3 Administration Guide.

8.1. Updating Red Hat Gluster Storage from 3.0.x to 3.1.x in the Offline Mode

If you have a distributed volume then you must opt for an offline upgrade. Red Hat Gluster Storage supports in-service software upgrade from Red Hat Gluster Storage 2.1 only for replicate and distributed-replicate volume.For more information about in-service software upgrade, see Section 9.2.3, “In-Service Software Upgrade”
To update NFS-Ganesha, perform the steps described in Section 8.2, “Updating NFS-Ganesha in the Offline Mode”


  • If dracut packages are previously installed, then exclude the dracut packages while updating to Red Hat Gluster Storage 3.1 during offline ISO update using the following command:
    # yum update -x dracut -x dracut-kernel
  • Offline upgrade results in a downtime as the volume is offline during upgrade.
To migrate the volume to a thinly provisioned volume in the offline mode, perform the following steps:
  1. Make a complete backup using a reliable backup solution. This Solution covers one possible approach:
    If you use an alternative backup solution:
    • Ensure that you have sufficient space available for a complete backup.
    • Copy the .glusterfs directory before copying any data files.
    • Ensure that no new files are created on Red Hat Gluster Storage file systems during the backup.
    • Ensure that all extended attributes, ACLs, owners, groups, and symbolic and hard links are backed up.
    • Check that the backup restores correctly before you continue with the migration.
  2. Delete the existing Logical Volume (LV) and recreate a new thinly provisioned LV. For more information, see
  3. Restore backed up content to the newly created thinly provisioned LV.
    When you are certain that your backup works, execute the following steps to update Red Hat Gluster Storage in the offline mode:
    # yum update
    The update process automatically restarts the glusterd management deamon. The glusterfs server processes, glusterfsd is not restarted by default since restarting this daemon affects the active read and write operations.
    After all the nodes in the cluster are updated, the volume must be restarted for the changes to be applied. Red Hat recommends that you restart the system when there are no active read and write operations running on the cluster.
    To restart the volume, run the following commands:
    # gluster volume stop volname 
    # gluster volume start volname
  4. When all nodes have been upgraded, run the following command to update the op-version of the cluster. This helps to prevent any compatibility issues within the cluster.
    # gluster volume set all cluster.op-version 30707