From 6b120c457193154b05307b4a200dd41fe11ce4ee Mon Sep 17 00:00:00 2001 From: Nikhil Ladha Date: Tue, 3 Nov 2020 12:09:39 +0530 Subject: [PATCH] Added a note for quota in upgrade procedure (#610) Added a note about how to fix the issue caused by the change in checksum computation while upgrading from a version less than 7.0 Signed-off-by: nik-redhat --- docs/Upgrade-Guide/Generic_Upgrade_procedure.md | 8 ++++++++ docs/Upgrade-Guide/upgrade_to_7.md | 6 ++++++ 2 files changed, 14 insertions(+) diff --git a/docs/Upgrade-Guide/Generic_Upgrade_procedure.md b/docs/Upgrade-Guide/Generic_Upgrade_procedure.md index 6dcf45b..fbdec0b 100644 --- a/docs/Upgrade-Guide/Generic_Upgrade_procedure.md +++ b/docs/Upgrade-Guide/Generic_Upgrade_procedure.md @@ -115,6 +115,14 @@ Perform the following steps post upgrading the entire trusted storage pool, - Proceed to [upgrade the clients](#upgrade-procedure-for-clients) to new-version version as well - Post upgrading the clients, for replicate volumes, it is recommended to enable the option `gluster volume set fips-mode-rchecksum on` to turn off usage of MD5 checksums during healing. This enables running Gluster on FIPS compliant systems. +#### If upgrading from a version lesser than Gluster 7.0 + +> **NOTE:** If you have ever enabled quota on your volumes then after the upgrade +is done, you will have to restart all the nodes in the cluster one by one so as to +fix the checksum values in the quota.cksum file under the `/var/lib/glusterd/vols// directory.` +The peers may go into `Peer rejected` state while doing so but once all the nodes are rebooted +everything will be back to normal. + ### Upgrade procedure for clients Following are the steps to upgrade clients to the new-version version, diff --git a/docs/Upgrade-Guide/upgrade_to_7.md b/docs/Upgrade-Guide/upgrade_to_7.md index 7a8e05d..33f2eab 100644 --- a/docs/Upgrade-Guide/upgrade_to_7.md +++ b/docs/Upgrade-Guide/upgrade_to_7.md @@ -9,6 +9,12 @@ Refer, to the [Upgrading to 4.1](./upgrade_to_4.1.md) guide and follow documented instructions, replacing 7 when you encounter 4.1 in the guide as the version reference. +> **NOTE:** If you have ever enabled quota on your volumes then after the upgrade +is done, you will have to restart all the nodes in the cluster one by one so as to +fix the checksum values in the quota.cksum file under the `/var/lib/glusterd/vols// directory.` +The peers may go into `Peer rejected` state while doing so but once all the nodes are rebooted +everything will be back to normal. + ### Major issues 1. The following options are removed from the code base and require to be unset