Hide Forgot
Description of problem: The global option gluster features.ganesha enable will write into the global 'option' file. Currently, only the snapshot feature writes into this file. But with CLI changes getting merged, NFS-Ganesha also writes into the same file. http://review.gluster.org/#/c/9538/ To handle concurrent multiple transactions correctly, a new lock has to be introduced on this file. Every operation using this file needs to contest for the new lock type. This bug is opened to track that change.
Review comments that need to addressed : 1. In the function, __glusterd_handle_ganesha_cmd , change the log level in gf_log to GF_LOG_DEBUG. 2. Remove validation of key/value in either commit/stage phase in CLI global option patch.
gluster vol info shows inconsistent values for features.ganesha. Check and fix in the same patch
REVIEW: http://review.gluster.org/10130 (NFS-Ganesha : Locking global options file) posted (#1) for review on master by Meghana M (mmadhusu@redhat.com)
REVIEW: http://review.gluster.org/10130 (NFS-Ganesha : Locking global options file) posted (#2) for review on master by Meghana M (mmadhusu@redhat.com)
REVIEW: http://review.gluster.org/10130 (NFS-Ganesha : Locking global options file) posted (#3) for review on master by Meghana M (mmadhusu@redhat.com)
REVIEW: http://review.gluster.org/10130 (NFS-Ganesha : Locking global options file) posted (#5) for review on master by Kaleb KEITHLEY (kkeithle@redhat.com)
REVIEW: http://review.gluster.org/10130 (NFS-Ganesha : Locking global options file) posted (#6) for review on master by Meghana M (mmadhusu@redhat.com)
COMMIT: http://review.gluster.org/10130 committed in master by Kaleb KEITHLEY (kkeithle@redhat.com) ------ commit 403a74da5d3287489829c629d42643b8b320ee62 Author: Meghana Madhusudhan <mmadhusu@redhat.com> Date: Mon Apr 20 10:41:47 2015 +0530 NFS-Ganesha : Locking global options file Global option gluster features.ganesha enable writes into the global 'option' file. The snapshot feature also writes into the same file. To handle concurrent multiple transactions correctly, a new lock has to be introduced on this file. Every operation using this file needs to contest for the new lock type. Change-Id: Ia8a324d2a466717b39f2700599edd9f345b939a9 BUG: 1200254 Signed-off-by: Meghana Madhusudhan <mmadhusu@redhat.com> Reviewed-on: http://review.gluster.org/10130 Reviewed-by: Avra Sengupta <asengupt@redhat.com> Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: soumya k <skoduri@redhat.com> Tested-by: NetBSD Build System Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com>
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