+++ This bug was initially created as a clone of Bug #1174625 +++ Description of problem: As of now, nfs server restarts whenever a snapshot is deactivated. Since nfs server does not manage snapshots of a volume, it should not get affected by deactivation of a snapshot. 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 Anand Avati on 2014-12-16 02:05:27 EST --- REVIEW: http://review.gluster.org/9280 (mgmt/glusterd: do not restart nfs server when snapshot is deactivated) posted (#1) for review on master by Raghavendra Bhat (raghavendra) --- Additional comment from Anand Avati on 2014-12-16 04:24:23 EST --- REVIEW: http://review.gluster.org/9280 (mgmt/glusterd: do not restart nfs server when snapshot is deactivated) posted (#2) for review on master by Raghavendra Bhat (raghavendra) --- Additional comment from Anand Avati on 2014-12-19 00:45:43 EST --- COMMIT: http://review.gluster.org/9280 committed in master by Kaushal M (kaushal) ------ commit 8484a88364b97ce3bc882db0f2da29633c03c1a5 Author: Raghavendra Bhat <raghavendra> Date: Tue Dec 16 12:34:19 2014 +0530 mgmt/glusterd: do not restart nfs server when snapshot is deactivated Change-Id: Ie5eaa2beb4446640b22873f91e17da90d1cd8fad BUG: 1174625 Signed-off-by: Raghavendra Bhat <raghavendra> Reviewed-on: http://review.gluster.org/9280 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaushal M <kaushal>
REVIEW: http://review.gluster.org/9425 (mgmt/glusterd: do not restart nfs server when snapshot is deactivated) posted (#1) for review on release-3.6 by Raghavendra Bhat (raghavendra)
COMMIT: http://review.gluster.org/9425 committed in release-3.6 by Raghavendra Bhat (raghavendra) ------ commit 443cda365ccc92597180dac59900dd5fbda43593 Author: Raghavendra Bhat <raghavendra> Date: Tue Dec 16 12:34:19 2014 +0530 mgmt/glusterd: do not restart nfs server when snapshot is deactivated > Change-Id: Ie5eaa2beb4446640b22873f91e17da90d1cd8fad > BUG: 1174625 > Signed-off-by: Raghavendra Bhat <raghavendra> > Reviewed-on: http://review.gluster.org/9280 > Tested-by: Gluster Build System <jenkins.com> > Reviewed-by: Kaushal M <kaushal> > Signed-off-by: Raghavendra Bhat <raghavendra> Change-Id: Ic5049f919fb444b45b3372a3b486183ed46d60f8 BUG: 1180404 Reviewed-on: http://review.gluster.org/9425 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaushal M <kaushal> Reviewed-by: Raghavendra Bhat <raghavendra>
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.6.2, please reopen this bug report. glusterfs-3.6.2 has been announced on the Gluster Developers mailinglist [1], packages for several distributions should already be or become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. The fix for this bug likely to be included in all future GlusterFS releases i.e. release > 3.6.2. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/5978 [2] http://news.gmane.org/gmane.comp.file-systems.gluster.user [3] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137