Chapter 7. Updating Red Hat Gluster Storage from 3.2.x to 3.2.y

Updating Red Hat Gluster Storage 3.2 in the offline mode

1. Make a complete backup using a reliable backup solution. This Knowledge Base solution covers one possible approach: https://access.redhat.com/solutions/1484053.
   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 https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Logical_Volume_Manager_Administration/thinprovisioned_volumes.html
3. Restore backed up content to the newly created thinly provisioned LV.
4. When you are certain that your backup works, stop all volumes.

   # gluster volume stop volname

5. Run the following commands to stop gluster services and update Red Hat Gluster Storage in the offline mode:
   On Red Hat Enterprise Linux 6:

   # service glusterd stop
   # pkill glusterfs
   # pkill glusterfsd
   # yum update

   On Red Hat Enterprise Linux 7:

   # systemctl stop glusterd
   # pkill glusterfs
   # pkill glusterfsd
   # yum update

   Wait for the update to complete.
6. Start glusterd.
   On Red Hat Enterprise Linux 6:

   # service glusterd start

   On Red Hat Enterprise Linux 7:

   # systemctl start glusterd

7. When all nodes have been updated, 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 31001

   Note

   31001 is the cluster.op-version value for Red Hat Gluster Storage 3.2.0. Refer to Section 1.5, “Supported Versions of Red Hat Gluster Storage” for the correct cluster.op-version value for other versions.
8. Start your volumes with the following command:

   # gluster volume start volname

9. If you had a meta volume configured prior to this upgrade, and you did not reboot as part of the upgrade process, mount the meta volume:

   # mount /var/run/gluster/shared_storage/

   If this command does not work, review the content of /etc/fstab and ensure that the entry for the shared storage is configured correctly and re-run the mount command. The line for the meta volume in the /etc/fstab file should look like the following:

   hostname:/gluster_shared_storage   /var/run/gluster/shared_storage/   glusterfs   defaults   0 0

10. If using NFS to access volumes, enable gluster-NFS using the following command:

    # gluster volume set volname nfs.disable off

    For example:

    # gluster volume set testvol nfs.disable off
    volume set: success

11. If you use geo-replication, restart geo-replication sessions when upgrade is complete.

    Important

    In Red Hat Gluster Storage 3.1 and higher, a meta volume is recommended when geo-replication is configured. However, when upgrading geo-replicated Red Hat Gluster Storage from version 3.0.x to 3.1.y, the older geo-replicated configuration that did not use shared volumes was persisted to the upgraded installation. Red Hat recommends reconfiguring geo-replication following upgrade to Red Hat Gluster Storage 3.2 to ensure that shared volumes are used and a meta volume is configured.

    To enable shared volumes, set the cluster.enable-shared-storage parameter to enable from the master node:

    # gluster volume set all cluster.enable-shared-storage enable

    Then configure geo-replication to use shared volumes as a meta volume by setting use_meta_volume to true.

    # gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL config use_meta_volume true

    For further information see the following sections in the Red Hat Gluster Storage 3.2 Administration Guide:

    • https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.2/html-single/Administration_Guide/index.html#chap-Managing_Red_Hat_Storage_Volumes-Shared_Volume
    • https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.2/html-single/Administration_Guide/index.html#chap-Managing_Geo-replication-Meta_Volume

    # gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL start

    Note

    As a result of BZ#1347625, you may need to use the force parameter to successfully restart in some circumstances.

    # gluster volume geo-replication MASTER_VOL SLAVE_HOST::SLAVE_VOL start force