Description of problem: after snapshot restoration, the geo-rep status gives misleading status. :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: # gluster --mode=script volume geo master 10.70.43.170::slave status MASTER NODE MASTER VOL MASTER BRICK SLAVE STATUS CHECKPOINT STATUS CRAWL STATUS -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- redlake.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick1/master_b1 10.70.43.170::slave Stable(Paused) N/A N/A redlake.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick5/master_b5 10.70.43.170::slave Stable(Paused) N/A N/A redlake.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick9/master_b9 10.70.43.170::slave Stable(Paused) N/A N/A redcell.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick3/master_b3 10.70.43.170::slave Stable(Paused) N/A N/A redcell.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick7/master_b7 10.70.43.170::slave Stable(Paused) N/A N/A # gluster --mode=script volume geo master 10.70.43.170::slave resume geo-replication session b/w master & 10.70.43.170::slave is not running on this node. geo-replication command failed # gluster --mode=script volume geo master 10.70.43.170::slave start Starting geo-replication session between master & 10.70.43.170::slave has been successful # gluster --mode=script volume geo master 10.70.43.170::slave status MASTER NODE MASTER VOL MASTER BRICK SLAVE STATUS CHECKPOINT STATUS CRAWL STATUS ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- redlake.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick1/master_b1 10.70.42.172::slave Initializing...(Paused) N/A N/A redlake.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick5/master_b5 10.70.42.172::slave Initializing...(Paused) N/A N/A redlake.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick9/master_b9 10.70.42.172::slave Initializing...(Paused) N/A N/A redeye.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick4/master_b4 10.70.42.208::slave Initializing...(Paused) N/A N/A # gluster --mode=script volume geo master 10.70.43.170::slave status MASTER NODE MASTER VOL MASTER BRICK SLAVE STATUS CHECKPOINT STATUS CRAWL STATUS -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- redlake.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick1/master_b1 10.70.42.172::slave Stable(Paused) N/A N/A redlake.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick5/master_b5 10.70.42.172::slave Stable(Paused) N/A N/A redlake.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick9/master_b9 10.70.42.172::slave Stable(Paused) N/A N/A # gluster --mode=script volume geo master 10.70.43.170::slave resume Resuming geo-replication session between master & 10.70.43.170::slave has been successful # gluster --mode=script volume geo master 10.70.43.170::slave status MASTER NODE MASTER VOL MASTER BRICK SLAVE STATUS CHECKPOINT STATUS CRAWL STATUS ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- redlake.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick1/master_b1 10.70.42.172::slave Active N/A Hybrid Crawl redlake.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick5/master_b5 10.70.42.172::slave Active N/A Hybrid Crawl redlake.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick9/master_b9 10.70.42.172::slave Active N/A Hybrid Crawl redeye.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick4/master_b4 10.70.42.208::slave Passive N/A N/A redeye.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick8/master_b8 10.70.42.208::slave Passive N/A N/A redeye.blr.redhat.com master /var/run/gluster/snaps/aadb8a3f77b44b1fa622abd50c6fbcb3/brick12/master_b12 10.70.42.208::slave Passive N/A N/A :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: From above command outputs, the after restoration, the geo-rep is not started but it says, stable(paused). Then geo-rep resume fails with misleading output, and geo-rep start succeeds. Which means, its just giving wrong status info. Version-Release number of selected component (if applicable):glusterfs-3.6.0.24-1.el6rhs How reproducible: didn't try to reproduce. Steps to Reproduce: 1. create and start a geo-rep relationship between master and slave. 2. create some files on master, and let it sync 3. follow steps to create a snapshot with geo-rep on both slave and master. 4. stop geo-rep. 5. stop slave and master volume. 6. restore snapshot on slave first and then master. 7. then check geo-rep status. Actual results: gives wrong status info like stable(paused) Expected results: it should say the proper status, like stopped(paused) if resume is required after start. or just stopped. Additional info: