Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1217939

Summary: Have a fixed name for common meta-volume for nfs, snapshot and geo-rep and mount it at a fixed mount location
Product: [Community] GlusterFS Reporter: Kotresh HR <khiremat>
Component: common-haAssignee: Kotresh HR <khiremat>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.7.0CC: asengupt, avishwan, bugs, gluster-bugs, jthottan, khiremat, kkeithle, meghana.m68, mmadhusu
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.7.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1210344 Environment:
Last Closed: 2015-05-14 17:29:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1210344    
Bug Blocks: 1186580, 1199352    

Description Kotresh HR 2015-05-03 07:22:15 UTC 
+++ This bug was initially created as a clone of Bug #1210344 +++

Description of problem:
Have a fixed name for common meta-volume for nfs, snapshot and geo-rep and mount it at a fixed mount location(/var/run/gluster/shared_storage/). Each component(nfs, snapshot, and geo-rep) should have their own repos inside the shared storage, and perform their operations in the shared storage

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Avra Sengupta on 2015-04-09 09:49:00 EDT ---

Using "gluster_shared_storage" as the volume name, and "/var/run/gluster/shared_storage/" as the location where it will be mounted.
Comment 1 Anand Avati 2015-05-03 07:28:11 UTC 
REVIEW: http://review.gluster.org/10503 (geo-rep: Adhering to the common storage for geo-rep) posted (#1) for review on release-3.7 by Kotresh HR (khiremat)
Comment 2 Anand Avati 2015-05-03 07:54:23 UTC 
REVIEW: http://review.gluster.org/10503 (geo-rep: Adhering to the common storage for geo-rep) posted (#2) for review on release-3.7 by Kotresh HR (khiremat)
Comment 3 Anand Avati 2015-05-03 07:54:26 UTC 
REVIEW: http://review.gluster.org/10506 (geo-rep: Fix minor bugs in meta-volume setup) posted (#1) for review on release-3.7 by Kotresh HR (khiremat)
Comment 4 Anand Avati 2015-05-04 09:25:26 UTC 
COMMIT: http://review.gluster.org/10503 committed in release-3.7 by Vijay Bellur (vbellur) 
------
commit 06cc6b5e4d59619b6c2b99ab86a44bf18c18ad1e
Author: Kotresh HR <khiremat>
Date:   Fri Apr 10 17:03:02 2015 +0530

    geo-rep: Adhering to the common storage for geo-rep
    
    Making geo-rep use the common storage shared by nfs,
    snapshot and geo-rep. The meta volume should be named
    as gluster_shared_storage, and it should be mounted
    at "/var/run/gluster/shared_storage/".
    
    Geo-rep will create a directory called 'geo-rep'
    in the meta-volume and all the lock files are created
    inside it.
    
    BUG: 1217939
    Change-Id: I1d88798376d68340e2b2eff018c7e4f0121a608a
    Signed-off-by: Kotresh HR <khiremat>
    Reviewed-on: http://review.gluster.org/10196
    Reviewed-on: http://review.gluster.org/10503
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Aravinda VK <avishwan>
Comment 5 Anand Avati 2015-05-04 14:23:05 UTC 
COMMIT: http://review.gluster.org/10506 committed in release-3.7 by Vijay Bellur (vbellur) 
------
commit 10d588fd849d92c3d7f4f86029b76098230c93b6
Author: Kotresh HR <khiremat>
Date:   Thu Apr 30 12:02:28 2015 +0530

    geo-rep: Fix minor bugs in meta-volume setup
    
    1. Access unreferenced access of fd:
           In meta volume configuration for geo-rep, if
       geo-rep directory is not created yet, open fails
       with no fd, but it is accessed in close(fd). So
       after creating 'geo-rep' directory in meta-volume,
       open the lock file to get fd.
    
    2. Fix volume_id in forming lock file name.
           For the very first time, gconf.volume_id would
       be null, as config is not reloaded yet. Hence, use
       'uuid' function to get the volume id.
    
    BUG: 1217939
    Change-Id: I06bf659ec506943c7ebf5303cc56a2e7748fbad0
    Signed-off-by: Kotresh HR <khiremat>
    Reviewed-on: http://review.gluster.org/10458
    Reviewed-on: http://review.gluster.org/10506
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Aravinda VK <avishwan>
Comment 6 Anand Avati 2015-05-05 09:05:20 UTC 
REVIEW: http://review.gluster.org/10555 (doc/geo-rep: Doc changes w.r.t common shared gluster meta volume) posted (#1) for review on release-3.7 by Kotresh HR (khiremat)
Comment 7 Kaleb KEITHLEY 2015-05-05 15:01:28 UTC 
for Ganesha/Gluster common-ha we used the common meta-volume. See https://bugzilla.redhat.com/show_bug.cgi?id=1213933 and http://review.gluster.org/10234

What is this BZ for exactly?

Thanks
Comment 9 Niels de Vos 2015-05-14 17:29:34 UTC 
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
Comment 10 Niels de Vos 2015-05-14 17:35:58 UTC 
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
Comment 11 Niels de Vos 2015-05-14 17:38:19 UTC 
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
Comment 12 Niels de Vos 2015-05-14 17:47:00 UTC 
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
Comment 13 Kotresh HR 2015-05-19 06:30:32 UTC 
Kaleb,

This bug is to track changes required to have common shared storage volume for nfs, geo-rep and snapsho. The requirement is using "gluster_shared_storage" as the volume name, and "/var/run/gluster/shared_storage/" as the location where it will be mounted.

Thanks,
Kotresh H R