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:
Using "gluster_shared_storage" as the volume name, and "/var/run/gluster/shared_storage/" as the location where it will be mounted.
REVIEW: http://review.gluster.org/10183 (snapshot/scheduler: Adhering to the common storage for scheduler) posted (#1) for review on master by Avra Sengupta (asengupt)
COMMIT: http://review.gluster.org/10183 committed in master by Krishnan Parthasarathi (kparthas) ------ commit 7a999ac6b1d0dad7e0b6ab6ee0868e97f76fada6 Author: Avra Sengupta <asengupt> Date: Thu Apr 9 19:39:12 2015 +0530 snapshot/scheduler: Adhering to the common storage for scheduler Making snapshot scheduler 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/". Each component(nfs, snapshot, and geo-rep) should have their own repos inside the shared storage, and perform their operations in the shared storage Change-Id: I4f670bf089c80037bd2b0716ddf743f48d7411ca BUG: 1210344 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/10183 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Aravinda VK <avishwan> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
The shared storage patch for snapshot component is already merged upstream. Moving the bug to geo-rep now, once they have a patch merged they can move it to nfs who can do the needful.
REVIEW: http://review.gluster.org/10196 (geo-rep: Adhering to the common storage for geo-rep) posted (#1) for review on master by Kotresh HR (khiremat)
The patch which addressess geo-rep changes required is sent. http://review.gluster.org/10196 The geo-rep admin guide needs to be updated. It will be done once the common steps to create meta volume is documented. Assigning the bug to nfs team.
REVIEW: http://review.gluster.org/10211 (NFS-Ganesha : Use common meta-volume for shared storage) posted (#1) for review on master by Meghana M (mmadhusu)
I have made NFS-Ganesha related changes and posted a patch. http://review.gluster.org/#/c/10211/
COMMIT: http://review.gluster.org/10211 committed in master by Kaleb KEITHLEY (kkeithle) ------ commit c37045c9ab572de7aa4c0dec5eeef4273ffd538a Author: Meghana Madhusudhan <mmadhusu> Date: Mon Apr 13 14:08:53 2015 +0530 NFS-Ganesha : Use common meta-volume for shared storage A fixed name and mount point is used to share the common volume required by various components. Make appropriate changes on the NFS-Ganesha to accomodate the commom meta-volume as the shared storage. Change-Id: I9c87e486c2bb3a414f9773c74ed46e111f3c9c14 BUG: 1210344 Signed-off-by: Meghana Madhusudhan <mmadhusu> Reviewed-on: http://review.gluster.org/10211 Reviewed-by: Kaleb KEITHLEY <kkeithle> Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System
REVIEW: http://review.gluster.org/10196 (geo-rep: Adhering to the common storage for geo-rep) posted (#2) for review on master by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/10196 committed in master by Vijay Bellur (vbellur) ------ commit b4d909003851e327d2cf448f9409cf5e31893579 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 have create a directory called 'geo-rep' in the meta-volume and all the lock files are created inside it. Change-Id: I82d0bff9be191f75f643606a9a21d53559047ac4 BUG: 1210344 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/10196 Reviewed-by: Aravinda VK <avishwan> Tested-by: NetBSD Build System Tested-by: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/10447 (doc/geo-rep: Doc changes w.r.t common shared gluster meta volume) posted (#1) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/10458 (geo-rep: Fix unreferenced access of fd) posted (#1) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/10458 (geo-rep: Fix minor bugs in meta-volume setup) posted (#2) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/10458 (geo-rep: Fix minor bugs in meta-volume setup) posted (#3) for review on master by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/10458 committed in master by Vijay Bellur (vbellur) ------ commit 3fe0c3c50eba9b64ebdd2abf0e8491d87078a440 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. Change-Id: I8381ab7a44bc800df25d596218466641c10937a4 BUG: 1210344 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/10458 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Aravinda VK <avishwan> Tested-by: NetBSD Build System
COMMIT: http://review.gluster.org/10447 committed in master by Vijay Bellur (vbellur) ------ commit c79e03ecd3cd9f2ffad52fad983b32133d8af787 Author: Kotresh HR <khiremat> Date: Mon Apr 13 11:56:35 2015 +0530 doc/geo-rep: Doc changes w.r.t common shared gluster meta volume Change-Id: I71c466537a191caa5c5a4a11e67df384c24c73ef BUG: 1210344 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/10447 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Aravinda VK <avishwan>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user