+++ This bug was initially created as a clone of Bug #1433506 +++ Description of problem: Master and slave geo-rep auxiliary mounts are not accessible to user to take client profile info or do any other client stack analysis. The mounts are lazy unmounted after changing the current directory to the respective mount point. So that only geo-rep worker has access to it. Version-Release number of selected component (if applicable): mainline How reproducible: Always Steps to Reproduce: 1. Setup geo-rep session between master and slave volume 2. Try to take the client side profile info of either master volume or slave volume Actual results: Not able to take client profile info of active geo-rep master and slave mount points on which I/O is happening Expected results: When needed, it should be possible to take client profile info of active geo-rep master and slave mount points on which I/O is happening Additional info: --- Additional comment from Worker Ant on 2017-03-17 16:02:14 EDT --- REVIEW: https://review.gluster.org/16912 (geo-rep: Optionally allow access to mounts) posted (#1) for review on master by Kotresh HR (khiremat) --- Additional comment from Worker Ant on 2017-03-19 23:33:40 EDT --- COMMIT: https://review.gluster.org/16912 committed in master by Vijay Bellur (vbellur) ------ commit e2a652ca6ba56235e6d64bf7df110afdc5f6ca27 Author: Kotresh HR <khiremat> Date: Fri Mar 17 13:03:57 2017 -0400 geo-rep: Optionally allow access to mounts In order to improve debuggability, it is important to have access to geo-rep master and slave mounts. With the default behaviour, geo-rep lazy unmounts the mounts after changing the current working directory into the mount point. It also cleans up the mount points. So only geo-rep worker has the access and it becomes impossible to take the client profile info and do any other client statck analysis. Hence the following new config is being introduced to allow access to mounts. gluster vol geo-rep <mastervol> <slavehost>::<slavevol> \ config access_mount true The default value of 'access_mount' is false. Change-Id: I53dce4ea86a6ffc979c82f9330e8954327180ca3 BUG: 1433506 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: https://review.gluster.org/16912 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: https://review.gluster.org/16978 (geo-rep: Optionally allow access to mounts) posted (#1) for review on release-3.10 by Kotresh HR (khiremat)
It's decided to take this in 3.11 as it's considered enhancement. Hence closing this.