Previously, when geo-replication was re-started or recovered from a 'Faulty' state, the unsynced xsync changelogs which were generated before stop or restart is not cleaned up. This resulted in consumption of inodes and space. With this fix, the unsynced changelogs are cleaned up whenever geo-replication starts or recovered from Faulty state resulting in saving inodes and space.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2018:2607
Description of problem: XSYNC changelog filling /var partition. Cleanup stale (unusable) XSYNC changelogs. Version-Release number of selected component (if applicable): glusterfs-geo-replication-3.8.4-54.el7rhgs.x86_64 Actual results: XSYNC changelog filling /var partition. Expected results: Cleanup stale (unusable) XSYNC changelogs. Additional info: Patch is already available upstream : patch : https://review.gluster.org/#/c/18983/ issue : https://github.com/gluster/glusterfs/issues/376