Bug 1201631 - Dist-geo-rep: With new Active/Passive switching logic, mgmt volume mountpoint is not cleaned up.
Summary: Dist-geo-rep: With new Active/Passive switching logic, mgmt volume mountpoint...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-13 07:06 UTC by Kotresh HR
Modified: 2015-05-10 03:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-10 03:57:27 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Kotresh HR 2015-03-13 07:06:43 UTC
Description of problem:
With new Active/Passive switching logic using fcntl lock on a file
residing in shared management volume. The management volume mount
will remain after geo-rep is stopped.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Setup geo-replication with management volume. 
2. start and stop geo-replication

Actual results:
Management volume mount point remains after geo-rep stop

Expected results:
Management mount point should be unmounted upon geo-rep stop

Additional info:
The management volume mount point choosen is predictable path and it uses
same mount point even after multiple geo-rep stop and start cycles. Hence, there won't be multiple mountpoints left over, it will be only one.

Comment 1 Aravinda VK 2015-05-10 03:57:27 UTC
With patches http://review.gluster.org/#/c/10196/ and http://review.gluster.org/#/c/10458/, Geo-rep is not mounting Meta volume internally. Closing this bug. Please reopen if the issue found again.


Note You need to log in before you can comment on or make changes to this bug.