Bug 764483 - (GLUSTER-2751) Volme stop must not be proceeded if gsync sessions are active for the volume
Volme stop must not be proceeded if gsync sessions are active for the volume
Status: CLOSED CURRENTRELEASE
Product: GlusterFS
Classification: Community
Component: glusterd (Show other bugs)
mainline
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: kaushik
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-04-14 00:57 EDT by kaushik
Modified: 2011-04-17 07:11 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description kaushik 2011-04-14 00:57:33 EDT

    
Comment 1 Anand Avati 2011-04-14 01:01:03 EDT
PATCH: http://patches.gluster.com/patch/6867 in master (mgmt/glusterd: fail the volume stop opeeration if Gsync sessions are active.)
Comment 2 Raghavendra Bhat 2011-04-17 04:11:13 EDT
Its fixed now. If volume stop is given with gsync running, then gluster cli reports it to the user.

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